threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "We discussed this idea in the past [1] and Robert recently again\nmentioned this in another thread [2]. Please see a rebased/revised\npatch attached with the mail. This is mostly similar to what I's\nsubmitted in [1] except some additions to also compute visibility\ncut-off XID. I also remove... |
[
{
"msg_contents": "Hello\n\nI tested some usage of LATERAL clause, and I found so LATERAL doesn't\nrespects difference between VOLATILE and IMMUTABLE functions.\n\nIs this behave expected?\n\n-- unexpected\npostgres=# select * from generate_series(1,3) g(v), LATERAL (SELECT random()) x;\n;\n v │ random\n──... |
[
{
"msg_contents": "I'm going to use PL/Python as an example, but I would also like to know\nif this could be applicable to other languages.\n\nWhen you do\n\nCREATE FUNCTION foo(...) ... LANGUAGE plpythonu\nAS $$\nsource code here\n$$;\n\nit internally creates a \"source file\" that contains\n\n---\ndef __plpyt... |
[
{
"msg_contents": "Hi,\n\nNow that XLRecPtr's are plain 64bit integers what are we supposed to use\nin code comparing and manipulating them? There already is plenty example\nof both, but I would like new code to go into one direction not two...\n\nI personally find direct comparisons/manipulations far easier to... |
[
{
"msg_contents": "Helllo\n\nI try to search simple solution and I didn't find anything. It is possible?\n\nRegards\n\nPavel Stehule\n\n\n-- \nSent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)\nTo make changes to your subscription:\nhttp://www.postgresql.org/mailpref/pgsql-hackers\n",
"msg_... |
[
{
"msg_contents": "Hello together,\n\nlast thursday I upgraded one of our 9.0.6 postgresql servers to 9.2.2 \nwith pg_upgrade. So far everything seemed to work but we now discover \nproblems with the enum types. If we run one specific query it breaks all \ntime with such an error message:\n\nERROR: invalid inte... |
[
{
"msg_contents": "Hello!\nI'm trying to update a database from version 9.0 to 9.1 by pg_upgrade.\nThe test is normal, but the actual conversion fails.\nThis is a bug from pg_upgrade?\nI just saw this in the newsletter similar error with a note that it has been fixed in 9.1.2, but I already install 9.1.7.\n\nMy... |
[
{
"msg_contents": "pg_basebackup -x is supposed to include all the required WAL files in \nthe backup, so that you have everything needed to restore a consistent \ndatabase. However, it's not including the timeline history files. \nUsually that's not a problem because normally you don't need to follow \nany old... |
[
{
"msg_contents": "We are regularly teaching PostgreSQL courses at linuxhotel.de.\nStarting from the course in November, PG doesn't compile anymore on\ntheir default Debian Squeeze install laptops they hand out to the\nparticipants. After ./configure && make, the error looks like this:\n\npostmaster/postmaster.... |
[
{
"msg_contents": "(This is different from the other issue related to timeline switches I \njust posted about. There's no timeline switch involved in this one.)\n\nIf you do \"pg_basebackup -x\" against a standby server, in some \ncircumstances the backup fails to restore with error like this:\n\nC 2012-12-17 1... |
[
{
"msg_contents": "\nI'm trying to use enum's in a database, but the java guys are telling me that they are having problems with inserts … reading from the database isn't a problem, but there appears to be an issue with converting from string -> enum when saving it back again …\n\nthey are using JPA2 / EJB + Ec... |
[
{
"msg_contents": "Hello\n\nthis patch was proposed\nhttp://archives.postgresql.org/pgsql-hackers/2012-08/msg00817.php and\nthere was no objections\n\n* there are no issue with patching\n* no warnings\n* code is clean and respect our source code policy\n* tested without errors\n\nMy last objections was satisfie... |
[
{
"msg_contents": "Basic stuff: \n------------ \n - Rebase of Patch is required. \n - Compiles cleanly without any errors/warnings \n - Regression tests pass. \n\nWhat it does: \n--------------------- \n This patch is useful when COPY command input/output are stored in\ncompression f... |
[
{
"msg_contents": "Greg Smith wrote:\n\n> In general, what I hope people will be able to do is switch over to \n> their standby server, and then investigate further. I think it's \n> unlikely that people willing to pay for block checksums will only have \n> one server. Having some way to nail down if the same b... |
[
{
"msg_contents": "On 12/18/2012 02:41 AM, Bruce Momjian wrote:\n\n On Mon, Dec 17, 2012 at 12:14:29PM +0100, Bernhard Schrader wrote:\n\n Hello together,\n\n last thursday I upgraded one of our 9.0.6 postgresql servers to\n 9.2.2 with pg_upgrade. So far everything seemed to work but we ... |
[
{
"msg_contents": "There are some system administration functions that have hardcoded\nsuperuser checks, specifically:\n\npg_reload_conf\npg_rotate_logfile\npg_read_file\npg_read_file_all\npg_read_binary_file\npg_read_binary_file_all\npg_stat_file\npg_ls_dir\n\nSome of these are useful in monitoring or maintena... |
[
{
"msg_contents": "Folks,\n\nSo as a test I tried to connect a group of 9.3 streaming replicas in a\ncircle (4 replicas). This was very easy to do:\n\n1. create r1 as replica of master\n2. create r2 as replica of r1\n3. create r3 as replica of r2\n4. create r4 as replica of r3\n5. start traffic on master\n6. s... |
[
{
"msg_contents": "Hackers,\n\nCurrently we can see each master's current replicas using\npg_stat_replication. However, there is no way from a replica, that I\nknow of, to figure out who its master is other than to look at\nrecovery.conf.\n\nWe should probably have a function, like pg_replication_master(), whi... |
[
{
"msg_contents": "Hello.\n\nI've noticed that, when implementing a FDW, it is difficult to use a plan which \nbest path is a parameterized path. This comes from the fact that the \nparameterized clause is not easily available at plan time.\n\nThis is what I understood from how it works:\n\n- The clauses comin... |
[
{
"msg_contents": "While playing with LDAP authentication, I discovered\ntwo documentation bugs.\n\nFirst, user and password for the first step in the\ntwo-step authentication mode are \"ldapbinddn\" and\n\"ldapbindpasswd\", not \"ldapbinduser\" and \"ldapbinddn\".\n\nThis bug has been there since 8.4.\n\nThe s... |
[
{
"msg_contents": "Hello again,\n\nwell, still everything is working.\n\nWhat information do you need to get into this issue?\n\nWell, so far i can say, we dont use ALTER TYPE ADD VALUE. We use some \nmore or less changed enum_add and enum_del (Which are appended at the \nend) to be able to change enums within ... |
[
{
"msg_contents": "In both checkpointer.c and bgwriter.c, we do this before entering the \nmain loop:\n\n /*\n * Use the recovery target timeline ID during recovery\n */\n if (RecoveryInProgress())\n ThisTimeLineID = GetRecoveryTargetTLI();\n\nThat seems reasonab... |
[
{
"msg_contents": "Groshev Andrey wrote:\n\n> >>>>> Mismatch of relation names: database \"database\", old rel public.lob.ВерсияВнешнегоДокумента$Документ_pkey, new rel public.plob.ВерсияВнешнегоДокумента$Документ\n\nThere is a limit on identifiers of 63 *bytes* (not characters)\nafter which the name is trunc... |
[
{
"msg_contents": "Simon Riggs wrote:\n\n> This is security, not spec compliance. By default, we need full\n> security.\n\nBut you are arguing that users should not be able to make something\nsecure if they, and everyone with the same permissions, could not\nlater access it. I thought about situations where I'v... |
[
{
"msg_contents": "Simon Riggs wrote:\n\n> I've argued that row security should apply to ALL commands by default.\n> Which is exactly the same default as Oracle, as well as being the\n> obvious common sense understanding of \"row security\", which does not\n> cause a POLA violation.\n> \n> I have no objection t... |
[
{
"msg_contents": "Andres Freund wrote:\n\n> I don't think it is that simple. Allowing inserts without regard for row\n> level restrictions makes it far easier to probe for data. E.g. by\n> inserting rows and checking for unique violations.\n\nUnless you want to go to a military-style security level system\nwhe... |
[
{
"msg_contents": "Simon Riggs wrote:\n> Kevin Grittner <kgrittn@mail.com> wrote:\n> \n>> I hope we can leave the syntax for this feature open to such\n>> specification, even if the initial implementation only supports\n>> limiting reads.\n> \n> Well, I hope the opposite: that we can support simple full securit... |
[
{
"msg_contents": "Hi,\n\none of our local users reported he's getting OOM errors on 9.2, although\non 9.1 the code worked fine. Attached is a simple test-case that should\ngive you an OOM error almost immediately.\n\nWhat it does:\n\n1) creates a simple table called \"test\" with one text column.\n\n2) creates... |
[
{
"msg_contents": "Bug #7758 seems to be a rediscovery of the behavior that Itagaki-san\ncomplained of a couple years ago:\nhttp://archives.postgresql.org/pgsql-hackers/2010-09/msg02035.php\n\nWhile reconsidering the various not-too-satisfactory fixes we thought of\nback then, I had a sudden thought. Instead o... |
[
{
"msg_contents": "I recently came across a scenario like this (tested on git head):\n\n----\nCREATE TABLE test (id int);\nCREATE INDEX test_idx1 ON test (id);\nCREATE INDEX test_idx2 ON test (id);\n\nCREATE TABLE test_copycat (LIKE test INCLUDING ALL);\n\\d test_copycat\n----\n\nWhy do we end up with only one ... |
[
{
"msg_contents": "Due to circumstances beyond my control (blame the power company), the\nfollowing buildfarm animals will be down from 27th December until 2nd\nJanuary:\n\nbaiji\nmastodon\nprotosciurus\ncastoroides\n\n--\nDave Page\nBlog: http://pgsnake.blogspot.com\nTwitter: @pgsnake\n\nEnterpriseDB UK: http:... |
[
{
"msg_contents": "Hi List,\n\n \n\n This might not be the right place to post, but I've got a minor patch for\npg_top and would like to submit it for review.\n\n \n\n Basically, the rpm version in the repositories pg_top92-3.6.2 doesn't work\nwith Postgres 9.2\n\n \n\n#define QUERY_PROCESSES \\\n\n ... |
[
{
"msg_contents": "The recent SET SCHEMA refactoring has changed the error message that\nyou get when trying to move a function into the schema that already\ncontains it.\n\nFor a table, as ever, you get:\n\nrhaas=# create table foo (a int);\nCREATE TABLE\nrhaas=# alter table foo set schema public;\nERROR: tab... |
[
{
"msg_contents": "This looks busted:\n\nrhaas=# create role clerks;\nCREATE ROLE\nrhaas=# create role bob in role clerks;\nCREATE ROLE\nrhaas=# create schema foo;\nCREATE SCHEMA\nrhaas=# grant usage on schema foo to bob, clerks;\nGRANT\nrhaas=# create aggregate\nfoo.sum(basetype=text,sfunc=textcat,stype=text,i... |
[
{
"msg_contents": "Kohei KaiGai wrote:\n\n> If system ensures writer's permission is always equivalent or\n> more restrictive than reader's permission, it also eliminates the\n> problem around asymmetric row-security policy between commands.\n\nI'm not sure we're understanding each other; so far people who\nfav... |
[
{
"msg_contents": "In order to implement the PARAMETER_DEFAULT column in the information\nschema I need a way to get the expressions out of the proargdefaults\ncolumn. pg_get_expr(proargdefaults, 0) gives me all expressions\ncomma-separated, but I need them individually. I think a function like\npg_get_list_... |
[
{
"msg_contents": "Kohei KaiGai wrote:\n\n>> I don't think I like ALTER TABLE as a syntax for row level\n>> security. How about using existing GRANT syntax but allowing a\n>> WHERE clause? That seems more natural to me, and it would make\n>> it easy to apply the same conditions to multiple types of\n>> operatio... |
[
{
"msg_contents": "Hi,\n\nCourtesy of me, Christmas comes a bit early this year. I wrote a patch \nwhich allows you to add STRICT into PERFORM and INSERT/UPDATE/DELETE \nwithout specifying an INTO clause. Observe:\n\n=# create table foo(a int);\nCREATE TABLE\n=# create function foof() returns void as $$ begin... |
[
{
"msg_contents": "When there is 'ssl=on' then postmaster calls SSL_CTX_new(),\nwhich asks for random number, thus requiring initialization\nof randomness pool (RAND_poll). After that all forked backends\nthink pool is already initialized. Thus they proceed with same\nfixed state they got from postmaster.\n\n... |
[
{
"msg_contents": "Hello guys, \n\nI've been finding performance issues when using a trigger to modify inserts on a partitioned table.\nIf using the trigger the total time goes from 1 Hour to 4 hours.\n\nThe trigger is pretty simple:\n\nCREATE OR REPLACE FUNCTION quotes_insert_trigger()\nRETURNS trigger AS $$\n... |
[
{
"msg_contents": "Simon Riggs wrote:\n\n> Each table has a single security clause. The clause doesn't enforce\n> that it must contain something that depends on role, but that is the\n> most easily understood usage of it. We do that to ensure that you can\n> embed the intelligence into a function, say hasRowLev... |
[
{
"msg_contents": "The PL/Python build on OS X is currently hardcoded to use the system\nPython install. If you try to override this when running configure, you\nget a mysterious mix-and-match build. If you want to build against your\nown Python build, or MacPorts or Homebrew, you can't.\n\nThis is straightfo... |
[
{
"msg_contents": "There has been discussion in the past of removing or significantly\nchanging the way streaming replication/point-in-time-recovery (PITR) is\nsetup in Postgres. Currently the file recovery.conf is used, but that\nwas designed for PITR and does not serve streaming replication well.\n\nThis all... |
[
{
"msg_contents": "In commit 11e131854f8231a21613f834c40fe9d046926387 we rearranged\nruleutils.c's handling of relation aliases to ensure that views can\nalways be dumped and reloaded even in the face of confusing table\nrenamings. I was reminded by\nhttp://archives.postgresql.org/pgsql-general/2012-12/msg0065... |
[
{
"msg_contents": "S1:\n\nrhaas=# create table foo (a int);\nCREATE TABLE\nrhaas=# begin;\nBEGIN\nrhaas=# lock foo;\nLOCK TABLE\n\nS2:\n\nrhaas=# grant all on foo to public;\nGRANT\nrhaas=# revoke all on foo from public;\nREVOKE\n\nThis seems quite obviously silly, given the amount of time and energy\nwe've spe... |
[
{
"msg_contents": "Hello all\n\nI found little bit strange behave of query search when I try to use\nnegation of prefix\n\npostgres=# select nazev from obce where to_tsvector('simple',nazev) @@\nto_tsquery('simple','skalice');\n nazev\n----------------------\n Klášterní Skalice\n Stříbrná Skalice\n Skali... |
[
{
"msg_contents": "Kohei KaiGai wrote:\n\n> RLS entry of wiki has not been updated for long time, I'll try to\n> update the entry for high-level design in a couple of days.\n\nThanks, I think that is essential for a productive discussion of\nthe issue.\n\nFor me, it would help tremendously if you could provide ... |
[
{
"msg_contents": "I promised to research allowing parallel execution of schema\ndump/restore, so I have developed the attached patch, with dramatic\nresults:\n\n\ttables git patch\n\t 1000 22.29 18.30\n\t 2000 30.75 19.67\n\t 4000 46.33 22.31\n\t 8000 81.09 29.27\n... |
[
{
"msg_contents": "I'm testing a checkout from a few days ago and trying to complete a day \nlong pgbench stress test, with assertions and debugging on. I want to \nmake sure the base code works as expected before moving on to testing \nchecksums. It's crashing before finishing though. Here's a sample:\n\n20... |
[
{
"msg_contents": "In some of my git branches I have\neditorialized src/backend/utils/misc/postgresql.conf.sample to contain my\nconfiguration preferences for whatever it is that that branch is for\ntesting. Then this gets copied to share/postgresql.conf.sample during\ninstall and from there to data/postgresql... |
[
{
"msg_contents": "The following commit is causing some compilation errors. \n\nc504513f83a9ee8dce4a719746ca73102cae9f13 \n\n\n\nError: \n../../../src/include/catalog/pg_aggregate.h:246: error: previous declaration\nof AggregateCreate was here \nmake: *** [pg_aggregate.o] Error 1 \n\n\n\n\nAuthor: Robert Haas <... |
[
{
"msg_contents": "Simon Riggs wrote:\n\n> Not really sure about the 100s of columns use case.\n> \n> But showing gain in useful places in these more common cases wins\n> my vote.\n> \n> Thanks for testing. Barring objections, will commit.\n\nDo we have any results on just a plain, old stock pgbench run, with\n... |
[
{
"msg_contents": "Hello\n\nCan we implement REGROLE type, that simplify role name <-> oid transformations?\n\nRegards\n\nPavel\n\n\n-- \nSent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)\nTo make changes to your subscription:\nhttp://www.postgresql.org/mailpref/pgsql-hackers\n",
"msg_date"... |
[
{
"msg_contents": "Hi all,\n\nCurrently I'm working on a large enterprise project that heavily uses \ntemporal features. We are using PostgreSQL database for data storage. \nNow we are using PL/pgSQL trigger-based and application-based solutions \nto handle with temporal data. However we would like to see this ... |
[
{
"msg_contents": "Here is a patch for the first part of the JSON API that was recently \ndiscussed. It includes the json parser hook infrastructure and \nfunctions for json_get and friends, plus json_keys.\n\nAs is, this exposes the json lexer fully for use by the hook functions. \nBut I could easily be persu... |
[
{
"msg_contents": "Hi all,\n\nThis proposal is about add a column \"datcreated\" on \"pg_database\" to store\nthe \"timestamp\" of the database creation.\n\nA couple weeks ago I had a trouble with a PostgreSQL instance, actually our\nERP had some strange behaviors with some data loss, but I searched for\nERRORs... |
[
{
"msg_contents": "Hello\n\nI rechecked performance of dynamic SQL and it is significantly slower\nin 9.2 than 9.1\n\n-- 9.1\npostgres=# create or replace function test() returns void as $$ begin\nfor i in 1..1000000 loop execute 'select 1'; end loop; end $$ language\nplpgsql;\nCREATE FUNCTION\npostgres=# \\tim... |
[
{
"msg_contents": "Hello all,\n\nA while ago, on pgsql-general, I raised the issue that the password\nstorage employed by postgres is a little weak and promised I'd look\ninto this during the holidays, so here are my findings.\n\nImplementing bcrypt instead of md5 is indeed rather straightforward;\njust move th... |
[
{
"msg_contents": "I committed background workers three weeks ago, claiming it worked on\nEXEC_BACKEND, and shortly thereafter I discovered that it didn't. I\nnoticed that the problem is the kludge to cause postmaster and children\nto recompute MaxBackends after shared_preload_libraries is processed; so\nthe m... |
[
{
"msg_contents": "SPI was invented before there was proper exception handling, so it\ncommunicates errors by return values. This makes programming with SPI\neither prone to errors of omission, or very ugly (ultimately, the\nstandard reasons why exceptions were invented).\n\nSo I was pondering whether we could... |
[
{
"msg_contents": "Hello,\n\nAfter long delay (sorry) here's a patch implementing what was\nhand-waved at in\nhttp://archives.postgresql.org/pgsql-hackers/2012-10/msg00176.php\n\nI am still something at a loss at how to test it besides prodding it\nby hand; it seems like it's going to involve infrastructure or\... |
[
{
"msg_contents": "Hi,\n\nToday, I tried to make fun with the new background worker processes in\n9.3, but I found something disturbing, and need help to go further.\n\nMy code is available on https://github.com/gleu/stats_recorder. If you\ntake a look, it is basically a copy of Alvarro's worker_spi contrib\nmo... |
[
{
"msg_contents": "Hello\n\nI am not sure, but maybe is time to introduce ANSI SQL syntax for\nfunctions' named parameters\n\nIt is defined in ANSI SQL 2011\n\n CALL P (B => 1, A => 2)\n\ninstead PostgreSQL syntax CALL ( B := 1, A := 2)\n\nPatch is very simple, but there are lot of questions about support\nprev... |
[
{
"msg_contents": "I'm creating a simple trigger that will be called during an insert and change the destination table.\nAll values are going to be preserved, just the destination table will be different.\n\nFrom what I see I can't modify trigdata->tg_relation.\n\nAll examples use: return Datum(trigdata->tg_tri... |
[
{
"msg_contents": "While tuning an application, I found the posts from 2003 recomending the\nuse of LOWER() and LIKE in place of ILIKE to take advantage of indices.\n\nFor this app, given the limitations of the upper-layer protocol it must\nsupport, that change replaced about 30 minutes of repeated seq scans wi... |
[
{
"msg_contents": "Hi all,\n\nAre there any plans on adding a rewriter hook? There are already exist \nparser, planner, executor hooks but there is no way to control rewriter \nfrom plugins.\n\nSome use cases:\n1. Complex rules in C language.\n2. Transforming an original query into a series of queries. For exam... |
[
{
"msg_contents": "The xlog code uses two different time zone formats at various times.\nHere is an example:\n\n2012-12-29 07:04:07.338 EST LOG: database system was interrupted; last known up at 2012-12-29 06:27:02 EST\n2012-12-29 07:04:26.347 EST LOG: last completed transaction was at log time 2012-12-29 06:... |
[
{
"msg_contents": "The cascading replication patch made a change to the way WAL files \nrestored from archive are handled. Since then, when a WAL file is \nrestored from archive, it's copied under the correct filename to \npg_xlog. Aside from supporting cascading replication, this has the \nadvantage that if th... |
[
{
"msg_contents": "Hi all\n\nFor some time it's been impossible to build PostgreSQL on 64-bit Windows\nby following the documentation's advice, as the version of Flex we\ndistribute on the PostgreSQL FTP site does not work on 64-bit Windows\nhosts. See this 2011 message (\nhttp://archives.postgresql.org/pgsql-h... |
[
{
"msg_contents": "Hello\n\nI am trying simulate hotstandby conflicts on 9.3, but without success.\n\nI have a basic hot standby configuration - on slave just \"hot_standby\n= on\", \"standby_mode = on\" and \"primary_conninfo\"\n\nhot standby node works well - but I would to generate conflict\n\nI create tabl... |
[
{
"msg_contents": "So, it turns out the reason I got no feedback on this tool, was that I\nforgot both to email about and to actually push the code to github :O\nSo this is actually code that's almost half a year old and that I was\nsupposed to submit for the first or second commitfest. Oops.\n\nSo, the tool an... |
[
{
"msg_contents": "On Thu, Aug 30, 2012 at 11:41 PM, Bruce Momjian <bruce@momjian.us> wrote:\n\n> On Sun, Jun 17, 2012 at 11:45:54PM +0800, Magnus Hagander wrote:\n> > On Sun, Jun 17, 2012 at 11:42 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:\n> > > Magnus Hagander <magnus@hagander.net> writes:\n> > >> Is there a re... |
[
{
"msg_contents": "Unify some tar functionality across different parts\n\nMove some of the tar functionality that existed mostly duplicated\nin both pg_dump and the walsender basebackup functionality into\nport/tar.c instead, so it can be used from both. It will also be\nused by pg_basebackup in the future, whi... |
[
{
"msg_contents": "Hi folks,\n\nI have a project which uses Postgres asynchronous notifications pretty\nheavily. It has a particularly Fun failure mode which causes the\nnotification queue to fill up. To better debug this problem I'd like\nto be able to monitor the size of the notification queue over time.\n\... |
[
{
"msg_contents": "Hi,\n\nwe are trying to integrate GMDA algorithm into postgresql. The operater\ndecouples grouping from\naggregation and we came up with the following syntax:\n\nSELECT d, u, COUNT(*b.u <= r.u*) AS ccu, COUNT(*b.d <= r.d*) AS ccd\nFROM b *GMDJOIN* r\nGROUP BY d, u\n\nThis select query should ... |
[
{
"msg_contents": "Hi all,\n\nWhen we execute 'make clean' the file 'src/backend/replication/repl_gram.h'\n is not removed.\n\nThe attached patch fix it.\n\nRegards,\n\n-- \nFabrízio de Royes Mello\nConsultoria/Coaching PostgreSQL\n>> Blog sobre TI: http://fabriziomello.blogspot.com\n>> Perfil Linkedin: http://... |
[
{
"msg_contents": "Hi,\n\nthe previously sent \"factor out pg_malloc and friends\" patch\nmay call exit() in case of OOM during allocation and as a consequence,\nPQfinish() won't get called, leaving an \"unexpected EOF from client\"\nin the log.\n\nLet's close this annoyance in pg_basebackup. The attached patch... |
[
{
"msg_contents": "On Windows, src/pl/plpython/Makefile has a rule whose target line expands to\nsomething like \"python33.def: C:/Windows/system32/python33.dll\". When doing a\nMinGW build with Cygwin's make-3.81, that line elicits an error:\n\nMakefile:69: *** target pattern contains no `%'. Stop.\n\nSeeing... |
[
{
"msg_contents": "Hi hackers.\n\nIs it by design that you can't setval(seq, value) a sequence to a value \nwhich returns the first value:\n\nSee the sample below for better explanation:\n\nhannu=# create sequence s;\nCREATE SEQUENCE\nhannu=# select nextval('s');\n nextval\n---------\n 1\n(1 row)\nhannu... |
[
{
"msg_contents": "On Sat, Dec 3, 2011 at 4:46 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:\n> I noticed the following object types don't have support for an ALTER ...\n> RENAME command:\n>\n> DOMAIN (but ALTER TYPE works)\n> FOREIGN DATA WRAPPER\n> OPERATOR\n> RULE\n> SERVER\n>\n> Are there any restric... |
[
{
"msg_contents": "Hello,\n\nI'm trying to print out the tuples in the b-tree nodes for analysis, but \nwhen iterate over more than the first entry of the tuples (scanKey++), I \nstrangely get the error below on query execution:\nERROR: relation \"simpletest\" does not exist\nLINE 1: SELECT * FROM simpletest W... |
[
{
"msg_contents": "I've been getting complaints lately about failures of parallel builds\nof the Fedora Postgres RPMs on the same machine. I just figured out\nwhat's going on: the pg_upgrade regression test script starts test\npostmasters using the default value of listen_addresses, which means\nthat they try ... |
[
{
"msg_contents": "Tolerate timeline switches while \"pg_basebackup -X fetch\" is running.\n\nIf you take a base backup from a standby server with \"pg_basebackup -X\nfetch\", and the timeline switches while the backup is being taken, the\nbackup used to fail with an error \"requested WAL segment %s has already... |
[
{
"msg_contents": "Hackers,\n\nAs a reminder, we are going to close the call for presentations for\npgCon on January 15th this year, in an effort to get speakers notified\nsooner. Please submit your talks as soon as you can.\n\n-- \nJosh Berkus\nPostgreSQL Experts Inc.\nhttp://pgexperts.com\n\n\n-- \nSent via ... |
[
{
"msg_contents": "Robert Haas wrote:\n> Christopher Browne <cbbrowne@gmail.com> wrote:\n\n>> these timestamps Should Not be captured or carried forward by\n>> pg_dump.\n\n>> If we put a creation time into pg_database or pg_class, then\n>> streaming replication will, as a \"physical\" replication\n>> mechanism,... |
[
{
"msg_contents": "Andrew Dunstan wrote:\n\n> I don't especially have a horse in the race, but ISTM that if you want \n> the information you want it to be able to persist across dump/restore, \n> at least optionally. If you can happily lose it when you're forced to \n> recover using a logical dump then it's not... |
[
{
"msg_contents": "Folks,\n\nThe PGCon Call for Papers went out last month. But you have about two weeks\nleft to respond. If you are doing something interesting with PostgreSQL, please submit\na proposal. You might be one of the backend hackers or work on a\nPostgreSQL related project and want to share your... |
[
{
"msg_contents": "The ./src/bin/pg_dump README contains several inoperable examples.\nFirst, this suggestion:\n\n| or to list tables:\n|\n| pg_restore <backup-file> --table | less\n\nseems bogus, i.e. the --table option requires an argument specifing\nwhich table to restore, and does not \"list tables\... |
[
{
"msg_contents": "Hello\n\nWhat is state of this issue?\nhttp://archives.postgresql.org/pgsql-hackers/2011-09/msg00423.php\n\nWe detect this issue in our servers - we use 9.1.6 on Linux\n\nlocktype | database | relation | page | tuple | virtualxid |\ntransactionid | classid | objid | objsubid | virtualtransact... |
[
{
"msg_contents": "Hi,\r\n I am a student in China. I have read some source code of postgreSQL, though only a little. I think maybe there is typo in this file: src\\backend\\catalog\\index.c. At line 649 in v9.2.0, line 653 in V9.2.2. The sentence is \" *indexInfo: same info executor uses to insert into th... |
[
{
"msg_contents": "Invent a \"one-shot\" variant of CachedPlans for better performance.\n\nSPI_execute() and related functions create a CachedPlan, execute it once,\nand immediately discard it, so that the functionality offered by\nplancache.c is of no value in this code path. And performance measurements\nsho... |
[
{
"msg_contents": "When adding a foreign key constraint on tableA which references\ntableB, why is an AccessExclusive lock on tableB necessary? Wouldn't a\nlock that prevents writes be sufficient, or does PostgreSQL have to\nmodify *both* tables in some fashion? I'm using PostgreSQL 8.4 on\nLinux.\n\n-- \nJon\n... |
[
{
"msg_contents": "Hi, hackers,\n\nThe attached is a patch to improve compression speeds with loss of\ncompression ratios in backend/utils/adt/pg_lzcompress.c. Recent\nmodern compression techniques like google LZ4 and Snappy inspreid\nme to write this patch. Thre are two points of my patch:\n\n1. Skip at most 2... |
[
{
"msg_contents": "Here is a patch for psql's \\l command to accept patterns, like \\d\ncommands do. While at it, I also added an \"S\" option to show system\nobjects and removed system objects from the default display. This might\nbe a bit controversial, but it's how it was decided some time ago that\nthe \\... |
[
{
"msg_contents": "Observation is that whenever a checkpoint happens and the wal_level\nconfigured is hot_standby then one standby snapshot XLOG gets written with\nthe information of \"running transaction\". \n\n\nSo if first time checkpoint happened at specified interval, it will create\nnew XLOG in LogStandby... |
[
{
"msg_contents": "On 7 January 2013 12:39, Amit Kapila <amit.kapila@huawei.com> wrote:\n\n> So We can modify to change this in function LogStandbySnapshot as below:\n> running = GetRunningTransactionData();\n> if (running->xcnt > 0)\n> LogCurrentRunningXa... |
[
{
"msg_contents": "Per this comment in lazy_scan_heap(), almost all tuple removal these days\nhappens in heap_page_prune():\n\n\t\t\t\tcase HEAPTUPLE_DEAD:\n\t\t\t\t\t/*\n\t\t\t\t\t * Ordinarily, DEAD tuples would have been removed by\n\t\t\t\t\t * heap_page_prune(), but it's possible that the tuple\n\t\t\t\t\t... |
[
{
"msg_contents": "For debugging PL/Python functions, I'm often tempted to write something\nlike\n\nrv = plpy.execute(...)\nplpy.info(rv)\n\nwhich prints something unhelpful like\n\n<PLyResult object at 0xb461d8d8>\n\nBy implementing a \"str\" handler for the result object, it now prints\nsomething like\n\n<PLy... |
[
{
"msg_contents": "Pg_upgrade by default (without --link) copies heap/index files from the\nold to new cluster. This patch implements parallel heap/index file\ncopying in pg_upgrade using the --jobs option. It uses the same\ninfrastructure used for pg_upgrade parallel dump/restore. Here are the\nperformance ... |
[
{
"msg_contents": "Reference: http://postgresql.1045698.n5.nabble.com/Simple-join-doesn-t-use-index-td5738689.html\n\nThis is a pretty common gotcha: user sets shared_buffers but misses\nthe esoteric but important effective_cache_size. ISTM\neffective_cache_size should always be >= shared buffers -- this is a\... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.