threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "Robert Haas wrote:\n\n> I heartily agree. I can say from firsthand experience that when minor\n> releases break things for customers (and they do), the customers get\n> *really* cranky. Based on recent experience, I think we should be\n> tightening our standards for what gets back-patched, no... |
[
{
"msg_contents": "Hi All,\n\nI am trying to build rpm of PostgreSQL, and the approach is building rpm for\n1. CentOS 6+\n2. Fedora 15+\n3. RedHat 6+\n4. OpenSUSE\n5. SuSE\n\nvia single spec file and not using any external rpm or repo while building\n\nthe problem i am facing right now is there is some dependen... |
[
{
"msg_contents": "Hello!\n\n I wrote to general ( [GENERAL] standby, pg_basebackup and last xlog file ) some times ago. but still hasn't got any feedback.\n\n\n Hello!\n\n Is there any reason why pg_basebackup has limitation in an online backup from the standby: \"The backup history file is not created in ... |
[
{
"msg_contents": "I've noticed a filename error in feedback messages from psql's '\\s' command\nwhen saving the command line history to a file specified by an absolute\nfilepath:\n\n psql (9.2.2)\n Type \"help\" for help.\n\n pgdevel=# \\s history.txt\n Wrote history to file \"./history.txt\".\n pgdevel=#... |
[
{
"msg_contents": "On Friday, January 11, 2013 11:12 PM Simon Riggs wrote:\nOn 11 January 2013 17:30, Amit kapila <amit(dot)kapila(at)huawei(dot)com> wrote:\n> On Friday, January 11, 2013 7:59 PM Alvaro Herrera wrote:\n> Simon Riggs wrote:\n>> On 28 December 2012 10:21, Simon Riggs <simon(at)2ndquadrant(dot)com... |
[
{
"msg_contents": "On 11 January 2013 15:57, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:\n\n>>>> I've moved this to the next CF. I'm planning to review this one first.\n>>\n>>> Thank you.\n>\n>> Just reviewing the patch now, making more sense with comments added.\n\n> Making more sense, but not yet making... |
[
{
"msg_contents": "Changing up the subject line because this is no longer a work in\nprogress nor is it pg_ping anymore.\n\nOn Sun, Jan 20, 2013 at 10:36 PM, Craig Ringer <craig@2ndquadrant.com> wrote:\n> On 01/21/2013 11:26 AM, Robert Haas wrote:\n>> On Sun, Jan 20, 2013 at 2:59 PM, Phil Sorber <phil@omniti.co... |
[
{
"msg_contents": "Attached is a patch that adds a note about the FATAL messages that\nappear in the logs if you don't pass a valid user or dbname to PQping\nor PQpingParams.\n\nThis was requested in the pg_isready thread.\n\n\n\n-- \nSent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)\nTo make c... |
[
{
"msg_contents": "A user reported an interesting issue today. After restoring a dump created\nwith --clean on a running application in his development environment his\napplication started complaining of missing tables despite those tables very\nclearly existing.\n\nAfter a little thinking, we determined that t... |
[
{
"msg_contents": "Folks,\n\nI've been working with Andrew Gierth (well, mostly he's been doing the\nwork, as usual) to add WITH ORDINALITY as an option for set-returning\nfunctions. In the process, he found a minor opportunity to clean up\nthe interface for $SUBJECT, reducing the call to a Single Point of\nTr... |
[
{
"msg_contents": "Sorry for the late response, I just happened to see this yesterday.\n\nRunning a general benchmark against the patch as Keven suggests is a good idea. \n\nAmit, can you supply the actual values you saw when running pgbench (the 3 values for each run)? I'd like to verify that the 1% difference... |
[
{
"msg_contents": "Since we've fixed a couple of relatively nasty bugs recently, the core\ncommittee has determined that it'd be a good idea to push out PG update\nreleases soon. The current plan is to wrap on Monday Feb 4 for public\nannouncement Thursday Feb 7. If you're aware of any bug fixes you think\nou... |
[
{
"msg_contents": "There have been some complaints[1][2] in the past about pg_ctl not\nplaying nice with relative path specifications for the datadir. Here's\na concise illustration:\n\n $ mkdir /tmp/mydata/ && initdb /tmp/mydata/\n $ cd /tmp/\n $ pg_ctl -D ./mydata/ start\n $ cd /\n $ pg_ctl -D /tmp/mydat... |
[
{
"msg_contents": "Hi all\n\nWould a committer be willing to pop some entries in .gitignore for\nWindows native build outputs?\n\n*.sln\n*.vcproj\n*.vcxproj\n\nIt'd make life easier when testing Windows changes.\n\n\n-- \n Craig Ringer http://www.2ndQuadrant.com/\n PostgreSQL Development, 24x7... |
[
{
"msg_contents": "Folks,\n\nPlease find attached a patch which implements the SQL standard\nUNNEST() WITH ORDINALITY. It doesn't stop there. Any function call\nin a FROM clause can now take WITH ORDINALITY, which appends a counter\n(ordinality) column to the columns the function outputs and produce\nresults ... |
[
{
"msg_contents": "Hi folks,\n\nI'm working on a project where I need to run some commands/functions when\nSELECT are executed on certain tables. I looked at the rule system and\nfound the following paragraph in the documentation:\n\n \"Currently, there can be only one action in an ON SELECT rule, and it\nmust... |
[
{
"msg_contents": "Test scenario to reproduce: \n 1. Start the server \n 2. create the user as follows \n ./psql postgres -c \"create user user1 superuser login\npassword 'use''1'\" \n\n 3. Take the backup with -R option as follows. \n ./pg_basebackup -D ../../... |
[
{
"msg_contents": "Improve concurrency of foreign key locking\n\nThis patch introduces two additional lock modes for tuples: \"SELECT FOR\nKEY SHARE\" and \"SELECT FOR NO KEY UPDATE\". These don't block each\nother, in contrast with already existing \"SELECT FOR SHARE\" and \"SELECT\nFOR UPDATE\". UPDATE comm... |
[
{
"msg_contents": "I get the following error when I try to compile just a specific binary\nin src/bin/scripts:\n\ngcc -O2 -Wall -Wmissing-prototypes -Wpointer-arith\n-Wdeclaration-after-statement -Wendif-labels\n-Wmissing-format-attribute -Wformat-security -fno-strict-aliasing\n-fwrapv -fexcess-precision=standa... |
[
{
"msg_contents": "On Wed, Jan 23, 2013 at 10:18 AM, Hari Babu <haribabu.kommi@huawei.com> wrote:\n> Test scenario to reproduce:\n> 1. Start the server\n> 2. create the user as follows\n> ./psql postgres -c \"create user user1 superuser login\n> password 'use''1'\"\n>\n> ... |
[
{
"msg_contents": "As a reminder, COPY FREEZE still does not issue any warning/notice if\nthe freezing does not happen:\n\n Requests copying the data with rows already frozen, just as they\n would be after running the <command>VACUUM FREEZE</> command.\n This is intended as a performance option f... |
[
{
"msg_contents": "Kevin Grittner wrote:\n\n> Applied with trivial editing, mostly from a pgindent run against\n> modified files.\n\nApplied back as far as 9.0. Before that code didn't match well\nenough for it to seem safe to apply without many hours of\nadditional testing.\n\nI have confirmed occurences of th... |
[
{
"msg_contents": "Folks,\n\nAs you know, there's a lot of people these days using SCHEMA for\nmulti-tenant application partitioning. One of them pointed out to me\nthat \"schema\" is missing from ALTER DEFAULT PRIVS; that is, there's no\nway for you to set default permissions on a new schema. For folks usin... |
[
{
"msg_contents": "The docs on bgworker twice refer to \"HOT standby\". I don't think that in\neither case, the \"hot\" needs emphasis, and if it does making it look like\nan acronym (one already used for something else) is probably not the way to\ndo it.\n\nPatch to HEAD attached.\n\nCheers,\n\nJeff\n\n\n-- \... |
[
{
"msg_contents": "Hello,\n\nsome app created tables ussing uppercase letters in table names (this app\nwas migrated from mysql). One tries to use \\d to search tables info:\n\nru=# \\d pnct_Board\nDid not find any relation named \"pnct_Board\".\n\nOf course, it works with \":\nru=# \\d \"pnct_Board\"\n ... |
[
{
"msg_contents": "Folks,\n\nAndrew Gierth asked me to send this out as his email is in a parlous\nstate at the moment. My comments will follow in replies. Without\nfurther ado:\n\n\nSQL2008 says, for 7.6 <table reference>\n\n6)\n a) If TR is contained in a <from clause> FC with no intervening <query\n ex... |
[
{
"msg_contents": "9.1 introduced delayed validation on FKs, and 9.2 on table constraints,\nhowever neither one has been useful due to lesser-locks on ALTER TABLE\nbeing reverted (see\nhttp://www.postgresql.org/message-id/1330350691-sup-1@alvh.no-ip.org),\npreventing the lock benefits during the VALIDATE stage.... |
[
{
"msg_contents": "Thanks for looking at this!\n\nNoah Misch wrote:\n\n> For the benefit of the archives, I note that we almost need not truncate an\n> unlogged materialized view during crash recovery. MVs are refreshed in a\n> VACUUM FULL-like manner: fill a new relfilenode, fsync it, and point the MV's\n> pg_... |
[
{
"msg_contents": "Noah Misch wrote:\n> On Thu, Jan 24, 2013 at 01:29:10PM -0500, Kevin Grittner wrote:\n>> Noah Misch wrote:\n>>> For the benefit of the archives, I note that we almost need not truncate an\n>>> unlogged materialized view during crash recovery. MVs are refreshed in a\n>>> VACUUM FULL-like manne... |
[
{
"msg_contents": "Hi,\n\nI have a bug pending that autovacuum fails to give priority to\nfor-wraparound tables. When xid consumption rate is high and dead tuple\ncreation is also high, it is possible that some tables are waiting for\nfor-wraparound vacuums that don't complete in time because the workers\nare ... |
[
{
"msg_contents": "I'm working with some DB2 users, converting them to Pg, and I'm a bit\nconfused about a certain class of SQLSTATE codes, specifically 02xxx \"No\ndata\" (http://www.postgresql.org/docs/9.2/static/errcodes-appendix.html)\n\nAs an example: I enable %e in log_line_prefix so I can see the SQLSTA... |
[
{
"msg_contents": "Noah Misch wrote:\n\n> The patch conflicts with git master; I tested against master@{2013-01-20}.\n\nNew patch rebased, fixes issues raised by Thom Brown, and addresses\nsome of your points.\n\n> PostgreSQL 8.3 clusters won't contain materialized views, so it doesn't really\n> matter whether ... |
[
{
"msg_contents": "Make pg_dump exclude unlogged table data on hot standby slaves\n\nNoted by Joe Van Dyk\n\nBranch\n------\nREL9_1_STABLE\n\nDetails\n-------\nhttp://git.postgresql.org/pg/commitdiff/1cc43979cf44db0b3da77e34493689fe13484fa0\n\nModified Files\n--------------\ndoc/src/sgml/ref/pg_dump.sgml | 3... |
[
{
"msg_contents": "pg_restore --single-transaction has the setup to make use of the new\nCOPY FREEZE optimization.\n\nHowever, I don't see us using COPY FREEZE for pg_restore\n--single-transaction. Shouldn't we do that? The problem is we would\nneed to have pg_dump emit the FREEZE, which would cause it not to... |
[
{
"msg_contents": "We are currently analyzing an issue at one of our customers PostgreSQL \ndatabase.\n\nThe current version is 9.1.6 (update to 9.1.7 is scheduled for next monday, \nno downtime possible before). It runs on POWER7 (pSeries 740) on an RHEL6.3 \n64-bit LPAR. The packages are built from PGDG SVN s... |
[
{
"msg_contents": "Don't think the attachment made it in the last mail. Attaching now.\n\n\nOn 25 January 2013 18:33, Dhruv Ahuja <dhruvahuja@gmail.com> wrote:\n\n> May I propose the attached patch.\n>\n> Points to note and possibly discuss:\n> (a) Only exit codes in do_* functions have been changed.\n> (b) The... |
[
{
"msg_contents": "A hashed SubPlan will not be used if it would need more than one\nbatch. Is there a fundamental reason for that, or just that no one\ngot around to adding it?\n\nA small decrease in work_mem leads to a 38000 fold change in estimated\nquery execution (and that might be accurate, as the actual... |
[
{
"msg_contents": "Hello Tom\n\nyou did comment\n\n! <----><------><------> * Non-null argument had better be an array.\nThe parser doesn't\n! <----><------><------> * enforce this for VARIADIC ANY functions\n(maybe it should?), so\n! <----><------><------> * that check uses ereport not just elog.\n! <----><---... |
[
{
"msg_contents": "Hi,\nI'm trying to build a. dll file to extend the postgres server with C functions. I'm using visual studio 2012 to build the dll, and PostgreSQL 9.2. I imported all directories postgres \"\\include\\server*\" But I'm having the errors:error C2011: 'timezone': 'struct' type redefinitionerror... |
[
{
"msg_contents": "Hi\n\nI found the ecpg programs can not output the native language messages which\ndefined in ecpglib6-9.x.mo.\nThe reason is a misstake in \"src/interfaces/ecpg/ecpglib/misc.c\",\nand i mad a patch for that.\n\nChen Huajun\n\n\n\n\n-- \nSent via pgsql-hackers mailing list (pgsql-hackers@post... |
[
{
"msg_contents": "I have a stress test of the of the WAL replay which panics the\ndatabase over and over again to make sure it recovers correctly.\n\nThis is in 9.3dev.\n\nThe test was eventually freezing up because of wraparound. The\nproblem was that, on fast enough hardware, the intentional crashes\nwere a... |
[
{
"msg_contents": "While testing Alexander's gistchoose patch, \"perf report\" showed that \nthe test case spent a surprisingly large amount of CPU time in \nExecScanHashBucket. That function just scans a hash bucket for matches, \nand it should be very quick as long as there are not many collisions.\n\nIt turn... |
[
{
"msg_contents": "Hi,\n\nI have tried other sources but to no avail. Could someone please tell me which tables in pg_catalog are effected by creating or dropping a trigger. If there is a work flow diagram or source code location you want to point me to rather than listing them that will be fine also. Some plon... |
[
{
"msg_contents": "I am working on reviewing the patch. Patch apply without warning/error on\nmaster branch. My findings are as following i.e.\n\n1. Behavior change in pg_ctl return value i.e.\n*\n*\n* Server already running*\n\na. Without Patch\n\ninst asif$ ./bin/pg_ctl -D data_test/ -l data_test.log star... |
[
{
"msg_contents": "Fast promote mode skips checkpoint at end of recovery.\npg_ctl promote -m fast will skip the checkpoint at end of recovery so that we\ncan achieve very fast failover when the apply delay is low. Write new WAL record\nXLOG_END_OF_RECOVERY to allow us to switch timeline correctly for downstream... |
[
{
"msg_contents": "Over in the thread about enhanced error fields, I claimed that\n\"constraints are uniquely named among those associated with a table,\nor with a domain\". But it turns out that that ain't necessarily so,\nbecause the code path for index constraints doesn't pay any attention\nto pre-existing ... |
[
{
"msg_contents": "All,\n\nIt's perhaps not the ideal time for a discussion but if I thought it would\nturn into a long discussion then I'd probably not post this due to the\ncurrent timing in the release cycle.\nThis is something I thought of while doing a restore on a 40ish GB database\nwhich has a few hundre... |
[
{
"msg_contents": "Hi!\n\nCalling \"SET TRANSACTION ISOLATION LEVEL ...\" outside a transaction\nblock has no effect. This is unlike \"LOCK ...\" and \"DECLARE foo\nCURSOR FOR ...\", which both raise an error. This is also unlike\nMySQL, where such a statement will affect the next transaction\nperformed. The... |
[
{
"msg_contents": "Hi,\n\nI took the liberty to create a new thread for $subject, because the main\ncomments I've been receiving about Event Triggers at this point is how\ndifficult it is to try and follow our discussions about them.\n\nIn order for everybody interested to be able to easily get the important\nb... |
[
{
"msg_contents": "Hi,\n\nAs the discussion about Event Triggers seems to be confusing at times\nfor people trying to follow at home, I've put together a wiki page that\ntries as making things clear about the use cases we want to solve and\nhow, and about what has been commited already and the remaining work to... |
[
{
"msg_contents": "I looked into the odd behavior noted recently on pgsql-novice that\nthe error context stack reported by plpgsql could differ between\nfirst and subsequent occurrences of the same error:\nhttp://www.postgresql.org/message-id/26370.1358539743@sss.pgh.pa.us\n\nThis seems to be specific to errors... |
[
{
"msg_contents": "Hi,\n\nThe fklocks patch moved HeapSatisfiesHOTandKeyUpdate (or rather\nHeapSatisfiesHOTUpdate back then) to be called way earlier in\nheap_update as its needed to know which lock level is\nrequired. Unfortunately the oid of the new tuple isn't yet setup at that\npoint.\n\nDue to this everyti... |
[
{
"msg_contents": "Heikki,\n\nI thought this was only a 9.3 issue, but it turns out to be\nreproduceable on 9.2.2. Basically, I did:\n\n1. master is queicent ... no writes occuring.\n2. createded cascading replica (reprep1) from replica (repmaster)\n3. reprep1 remains \"in recovery mode\" until a write occurs ... |
[
{
"msg_contents": "\nWhat's the best way for me to find out if a given parameter of a \nfunction is a constant? The context is that it's expensive to process, \nand in most cases will in fact be a constant, so if it is in fact a \nconstant I'd like to process it once and stash the results.\n\ncheers\n\nandrew\n... |
[
{
"msg_contents": "Hi everyone,\n\nWe are experiencing a strange situation after upgrading our Postgres from\n8.4 to 9.1 and our OS from Debian 6 to Ubuntu 12.04 LTS.\n\nWe have an application where we are collecting timestamp-based data. Since\na month of data goes over 30M rows (and growing each month), we de... |
[
{
"msg_contents": "Hello\n\nnow a most \"hard\" work is done and I would to enable access to new\nerror fields from plpgsql.\n\nthese new fields are column_name, constraint_name, datatype_name,\ntable_name and schema_name.\n\nThis proposal has impact on two plpgsql statements - RAISE and GET\nSTACKED DIAGNOSTIC... |
[
{
"msg_contents": "On Fri, Feb 1, 2013 at 6:10 PM, Pavan Deolasee <pavan.deolasee@gmail.com>wrote:\n\n>\n>\n>\n>>\n>> 2012-12-05 00:44:23 EET LOG: automatic analyze of table\n>> \"fleet.fleet.vehicle_position\" system usage: CPU 4.46s/0.61u sec elapsed\n>> 465.09 sec\n>>\n>\n> This is the interesting piece of ... |
[
{
"msg_contents": "\nfmgr.c contains this:\n\n /*\n * !!! OLD INTERFACE !!!\n *\n * fmgr() is the only remaining vestige of the old-style caller support\n * functions. It's no longer used anywhere in the Postgres\n distribution,\n * but we should leave it around for a release or ... |
[
{
"msg_contents": "I've been able to reproduce the problem reported by Pius Chan in bug\n#7819. With some logging added that prints the OldestXmin values used\nby vacuum and cluster operations, the reason is fairly clear:\n\n2013-02-01 13:41:12 EST 8011 LOG: vacuuming \"test\" with OldestXmin 1760160 FreezeLi... |
[
{
"msg_contents": "create extension hstore with schema pg_catalog;\nalter extension hstore set schema public;\nERROR: 0A000: cannot remove dependency on schema pg_catalog because it\nis a system object\ndrop extension hstore; -- works\n\nI've seen this happen cleaning up after mistakenly misplaced extensions.... |
[
{
"msg_contents": "I have encountered two unrelated flaws in the psql table output.\n\nFirst, when using unaligned vertical mode (\\a \\x on), there is always an\nempty line after the last record. This also means that an empty result\nset prints an empty line, instead of nothing.\n\nSecond, when using aligned ... |
[
{
"msg_contents": "(sending this again; it was eaten by the ethernet)\n\nHeikki,\n\nI thought this was only a 9.3 issue, but it turns out to be\nreproduceable on 9.2.2. Basically, I did:\n\n1. master is queicent ... no writes occuring.\n2. createded cascading replica (reprep1) from replica (repmaster)\n3. repr... |
[
{
"msg_contents": "Hi,\n\nI'm having trouble with range types and btree_gist - after some playing \nI believe it's\ncaused by a bug in how btree_gist handles text columns. All this is on \nfreshly compiled\n9.2.2.\n\nI'm trying to achieve almost exactly what's described in the second \nexample on\n\n \nhttp:... |
[
{
"msg_contents": "Hello\n\nI propose enhancing GET DIAGNOSTICS statement about new field\nPG_CONTEXT. It is similar to GET STACKED DIAGNOSTICS'\nPG_EXCEPTION_CONTEXT.\n\nMotivation for this proposal is possibility to get call stack for\ndebugging without raising exception.\n\nThis code is based on cleaned cod... |
[
{
"msg_contents": "Hello,\nAfter a discussion on IRC in #postgresql, I had a feature suggestion and it\nwas suggested I write it up here.\n\nI have a large (200GB, 1.7b rows) table with a number of columns, but the\ntwo of interest here are a hstore column, tags and a postgis geometry\ncolumn, geom. \n\nThere i... |
[
{
"msg_contents": "Mark vacuum_defer_cleanup_age as PGC_POSTMASTER.\n\nFollowing bug analysis of #7819 by Tom Lane\n\nBranch\n------\nREL9_0_STABLE\n\nDetails\n-------\nhttp://git.postgresql.org/pg/commitdiff/59f800d05866ef447e1337bc8f2c9a54063f6eba\n\nModified Files\n--------------\ndoc/src/sgml/config.sgml ... |
[
{
"msg_contents": "Ok, thanks for the info. I'll look into that and I'll also post info from some of our production systems (we've deployed a 9.1-backpatched version about 2 weeks ago).\n\nT.\n\n-------- Původní zpráva --------\nOd: Jeff Janes <jeff.janes@gmail.com> \nDatum: \nKomu: Tomas Vondra <tv@fuzzy.cz> ... |
[
{
"msg_contents": "This patch came up from discussion about pg_isready.\n\nPQconninfoParseParams is similar to PQconninfoParse but takes two\narrays like PQconnectdbParams. It essentially exposes\nconninfo_array_parse().\n\nPQconninfodefaultsMerge essentially exposes conninfo_add_defaults().\nIt allows you to p... |
[
{
"msg_contents": "I'm hoping that someone familiar with sepgsql can review this\nportion of the materialized view patch and comment on whether it is\nthe best approach for dealing with the integration of these two\nfeatures. Basically, the patch as it stands treats a materialized\nview as a table for purposes... |
[
{
"msg_contents": "There is a bug in hot_standby_feedback that causes the xmin of the\nwalsender process to not be reset when hot_standby_feedback is turned\noff after it had previously sent at least one feedback message.\n\nClearly, that is a bad thing and deserves backpatching to 9.1, unless\nI hear otherwise... |
[
{
"msg_contents": "Hi Josh,\n\nI was quite busy last few months and I didn't have time to devote to this\ntopic. I have read the feedbacks and want to make things move now.\n\nI suggest, we can start by discussing the design of my solution:\nhttps://wiki.postgresql.org/wiki/SQL2011Temporal\n\nI expect any criti... |
[
{
"msg_contents": "I just noticed that contrib programs don't build in USE_PGXS=1\nenvironment:\n\n$ pwd\n/pgsql/build/HEAD/contrib/pg_upgrade\n$ LC_ALL=C USE_PGXS=1 make \nmake: *** No rule to make target `check.o', needed by `pg_upgrade'. Stop.\n$ LC_ALL=C make \n [works]\n\nIs this expected?\n\n-- \nÁlvaro ... |
[
{
"msg_contents": "Hi,\n\npg_xlogdump needs access to the *_desc functions for each rmgr. We\nalready moved forward quite a bit by splitting those functions out of\ntheir containing files; so now they are compilable separately. Good.\nThe remaining task is enabling the code to find those functions in the\nfir... |
[
{
"msg_contents": "Stamp 9.1.8.\n\nBranch\n------\nREL9_1_STABLE\n\nDetails\n-------\nhttp://git.postgresql.org/pg/commitdiff/69c026512f1141a92dca118768d858e59d76a994\n\nModified Files\n--------------\nconfigure | 18 +++++++++---------\nconfigure.in | 2 +-\ndoc/bu... |
[
{
"msg_contents": "There was some discussion about unifying backend and frontend\ncode/headers for palloc et al, particularly so that programs that want\nto mix both can be easily compiled; see \nhttp://www.postgresql.org/message-id/20130118150629.GC29501@alap2.anarazel.de\nfor what I believe to be the latest a... |
[
{
"msg_contents": "get_progname() returns a strdup()'d value. Shouldn't it then be simply\nchar * and not const char *? Otherwise free() complains loudly without\na cast.\n\ndiff --git a/src/include/port.h b/src/include/port.h\nnew file mode 100644\nindex 99d3a9b..2d6a435\n*** a/src/include/port.h\n--- b/src/in... |
[
{
"msg_contents": "Per the support policy at\nhttp://www.postgresql.org/support/versioning/\nthe 8.3.x branch has an EOL date of February 2013.\n\nThat means that, barring discovery of a bug so bad that we decide to\nmake a fresh set of update releases within the month, the just-wrapped\n8.3.23 is the last rele... |
[
{
"msg_contents": "Hello. This was bounced my way via IRC[1] and I'm kicking an updated version of the patch upstream for review and committing.\n\nCurrently src/port/pgcheckdir.c will reject non-empty directories, which is an issue during initdb(1) when PGDATA is also the mount point for filesystems that suppo... |
[
{
"msg_contents": "I found a small bug in the implementation of LDAP connection\nparameter lookup.\n\nAs documented in\nhttp://www.postgresql.org/docs/current/static/libpq-ldap.html\nprocessing should continue after a failed attempt\nto connect to an LDAP server.\n\nThe code in src/interfaces/libpq/fe-connect.c... |
[
{
"msg_contents": "hi,\n\nAs reported in BUG #7715 [1], hstore's use of ? as an operator conflicts \nwith JDBC's bind variables.\n\nI think we could just alias ? to ~ and tell JDBC users to use that \ninstead. [2]\n\nBest,\nSeamus\n\n[1] \nhttp://www.postgresql.org/message-id/E1TeIju-0003qb-WD@wrigleys.postgres... |
[
{
"msg_contents": "For many aggregate functions it is necessary to store the actual column values in the aggregate state and then do whatever calculation across them in the final function. In many examples this is done by using array_append as the sfunc and then a custom plpgsql function as the final function ... |
[
{
"msg_contents": "Hi all,\n\nI have deferred constraint update trigger in which I need to set same\ntimestamp to all modified rows. The time needs to be the time of first\ninvocation of this trigger fuction in transaciton. My intention is to set\ncommit time to rows modified in transaction.\n\nSo I need functi... |
[
{
"msg_contents": "Hello Everyone,\n\nI am using postgres 9.2 and when executing function dblink facing a fatal\nerror while trying to execute dblink_connect as follows:\n\n * SELECT * FROM dblink_connect('host=127.0.0.1 port=5432 dbname=postgres\npassword=test')*\n\n *ERROR*: could not establish connectio... |
[
{
"msg_contents": "Hackers,\n\nWhile playing with Andrew’s JSON enhancements, I noticed this:\n\n david=# select * From json_each_as_text('{\"baz\": null}'::json);\n key | value \n -----+-------\n baz | null\n\nIt is returning 'null'::text there, not NULL::text. I had expected the latter, because ... |
[
{
"msg_contents": "Forgive the top-reply.\n\nAfter reading the discussion, I'm in favor of the \"philosophically \ncorrect\" approach rather than the usually-technically-correct approach. \nThat is, display the warning, but let the sysadmin/dba do what they \nneed/want to do and trust that, most of the time, t... |
[
{
"msg_contents": "Hackers,\n\nAs an occasional CommitFest manager, I'm keenly aware of the makeshift\nnature of the CommitFest app. If we want to go on using it -- and if we\nwant to attract additional reviewers -- we need to improve it\nsubstantially. What Robert built for us was supposed to be a second\ndr... |
[
{
"msg_contents": "tl;dr\n\nScala/JRuby/Clojure (any JVM-based language) + Postgres + hstore = \nawesome... why not just add a few lines to hstore--1.2.sql and make sure \nthat all operators are available and indexable?\n\nhi Andrew, hi merlin,\n\n> use the existing \"exist()\" function\n\nEXIST() can't use hst... |
[
{
"msg_contents": "While stress testing Pavan's 2nd pass vacuum visibility patch, I realized\nthat vacuum/visibility was busted. But it wasn't his patch that busted it.\n As far as I can tell, the bad commit was in the\nrange 692079e5dcb331..168d3157032879\n\nSince a run takes 12 to 24 hours, it will take a wh... |
[
{
"msg_contents": "Through the work on the patch [1], I had a question about the psql \\copy\ncommand. We are permitted 1) but not permitted 2):\n1) \\copy foo from stdin ;\n2) \\copy foo from stdin;\nIs this intentional? I think it would be better to allow for 2). Attached is a\npatch.\n\nThanks,\n\nBest re... |
[
{
"msg_contents": "Hi,\n\nit seems there's a issue in instrument.c that may have significant\nperformance impact for some plans when running explain analyze with\n\"TIMING OFF\".\n\nThere's this piece of code in InstrStartNode:\n\n if (instr->need_timer && INSTR_TIME_IS_ZERO(instr->starttime))\n INSTR... |
[
{
"msg_contents": "I found a comment typo. Please find attached a patch.\n\nBest regards,\nEtsuro Fujita\n\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",
"msg_date": "Fri, 8 Feb 2013 14:... |
[
{
"msg_contents": "\n\nHello all and Heikki personally\nThank you for your answer\n\nI have some new points:\n\n\n21.01.2013, 10:08 +02:00 от Heikki Linnakangas <hlinnakangas@vmware.com>:\n>On 21.01.2013 09:14, Миша Тюрин wrote:\n>> Is there any reason why pg_basebackup has limitation in an online backup fro... |
[
{
"msg_contents": "Hi,\n\nThe 9.2.3 release notes say:\n* Fix pg_upgrade's -O/-o options (Bruce Momjian)\n\nYou got it the wrong way around, he was the one who introduced the bug! ;)\n\nI originally found, debugged and provided the fix:\nhttp://www.postgresql.org/message-id/CABRT9RBy1uRTMY-DfLDgBPCp+ZQU36M_+BLD... |
[
{
"msg_contents": "I was looking at the vacuum/visibility bug that Jeff Janes reported\nand brought up the server with the data directory he has shared. With\nhis configuration,\n\n# - Checkpoints -\n\ncheckpoint_segments = 1 # in logfile segments, min 1, 16MB each\ncheckpoint_timeout = 30s # range 3... |
[
{
"msg_contents": "Hi,\n\ni have created a normal user (no superuser) akretschmer01 and another normal\nuser ak02. All fine.\nThe first user is the owner of the db.\n\n\nAs user akretschmer01 i granted:\n\n-bash-4.1$ psql -U akretschmer01 db115150\npsql (9.1.8)\nType \"help\" for help.\n\ndb115150=> grant all o... |
[
{
"msg_contents": "Over in Fedora-land they're trying to institute support for ARM64,\nwhich among other things means autoconf 2.69 or later:\nhttp://lists.fedoraproject.org/pipermail/devel/2013-February/178273.html\n\nWe are behind the curve.\n\n\t\t\tregards, tom lane\n\n\n-- \nSent via pgsql-hackers mailing ... |
[
{
"msg_contents": "\n Hi all\n\n I've got suspicious behavior for transaction cooked with deferrable trigger. if trigger has update on row of his target table we get infinite \"recursion\" without limitation of stack depth. \n\n trigger -> update -> trigger -> update -> ... ... -- infinite pending list :)\n... |
[
{
"msg_contents": "Hello,\n\nI'd like to submit the following patch that extends backup.sgml with a bit of practical but important information.\n\nProject: postgresql\nPatch filename: backup.sgml-cmd-v001.patch\n\nThe patch extends backup.sgml and adds practical information on custom format backups approach. Ba... |
[
{
"msg_contents": "commit 381d4b70a9854a7b5b9f12d828a0824f8564f1e7 introduced some\ncompiler warnings:\n\nassert.c:26: warning: no previous prototype for 'ExceptionalCondition'\nelog.c: In function 'pg_re_throw':\nelog.c:1628: warning: implicit declaration of function 'ExceptionalCondition'\nelog.c:1630: warnin... |
[
{
"msg_contents": "psql: Improve expanded print output in tuples-only mode\n\nWhen there are zero result rows, in expanded mode, \"(No rows)\" is\nprinted. So far, there was no way to turn this off. Now, when\ntuples-only mode is turned on, nothing is printed in this case.\n\nBranch\n------\nmaster\n\nDetails... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.