threads listlengths 1 2.99k |
|---|
[
{
"msg_contents": "hiu\nI have weird situation.\npg 9.1.2, compilet by our own script from source, on 10+ machines.\non fours machines, pg_dump -s <database_name> - dumps with data!:\n\npostgres@machine:~$ pg_dump --verbose --schema-only dbname > q\n...\npg_dump: creating TABLE x1\npg_dump: restoring data for ... |
[
{
"msg_contents": "I've been prototyping the double-write buffer idea that Heikki and Simon\nhad proposed (as an alternative to a previous patch that only batched up\nwrites by the checkpointer). I think it is a good idea, and can help\ndouble-writes perform better in the case of lots of backend evictions.\nIt... |
[
{
"msg_contents": "It looks like initdb doesn't fsync all the files it creates, e.g. the\nPG_VERSION file.\n\nWhile it's unlikely that it would cause any real data loss, it can be\ninconvenient in some testing scenarios involving VMs.\n\nThoughts? Would a patch to add a few fsync calls to initdb be accepted?\nI... |
[
{
"msg_contents": "Hi,\n\nI'm using latest git master (latest entry\n0816fad6eebddb8f1f0e21635e46625815d690b9) and I'm getting an error\nwhen trying to create a large data set with pgbench:\n\nthom@swift:~/Development$ createdb pgbench\nthom@swift:~/Development$ pgbench -i -s 100 pgbench\nNOTICE: table \"pgben... |
[
{
"msg_contents": "create user foouser;\ncreate tablespace temptblspc location '/tmp/tmptblspc';\nalter user foouser set temp_tablespaces='temptblspc';\n\nRun pg_dumpall. It will produce a dump like:\n\n...\nCREATE ROLE foouser;\nALTER ROLE foouser WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB \nLOGIN NOREPL... |
[
{
"msg_contents": "I thought it'd be a good idea to put in some basic test cases for the\nEvalPlanQual code using the isolationtester infrastructure. While\nfooling with it, I soon ran into this restriction:\n\n\t\tif (p->nsteps != nallsteps)\n\t\t{\n\t\t\tfprintf(stderr, \"invalid number of steps in permutati... |
[
{
"msg_contents": "When you try to use the NEW variable in a statement-level trigger, you get\n\nERROR: record \"new\" is not assigned yet\nDETAIL: The tuple structure of a not-yet-assigned record is indeterminate.\n\nwhich is not too friendly, given that people sometimes forget to specify\nFOR EACH <sth> at ... |
[
{
"msg_contents": "----- Π¦ΠΈΡΠ°Ρ ΠΎΡ Oleg Bartunov (oleg@sai.msu.su), Π½Π° 28.01.2012 Π² 21:04 ----- \n\n> I suggest you work on more general approach, see \n> http://www.sai.msu.su/~megera/wiki/2009-08-12 for example. \n> \n> btw, I don't like you changed ts_rank_cd arguments. \n\nHello Oleg, \n\nThanks for the feed... |
[
{
"msg_contents": "Given a freshly created table (not vacuumed), and a query that uses an\nindex-only scan, for example:\n\nCREATE TABLE foo(a int PRIMARY KEY);\nINSERT INTO foo SELECT * FROM generate_series(1,1000000);\nANALYSE foo;\n\nEXPLAIN ANALYSE SELECT count(*) FROM foo WHERE a <= 10000;\n\n ... |
[
{
"msg_contents": "We apologize that http://www.bsdcan.org/ was offline for 12 hours from early Sunday morning.\n\nThe deadline for submissions has been extended to Tuesday 31 January.\n\nPGCon 2012 will be held 17-18 May 2012, in Ottawa at the University of\nOttawa. It will be preceded by two days of tutorial... |
[
{
"msg_contents": "Hi,\n\nIs it possible to use a standby instance as a master/primary for another\nstandby in Postgres 9.0? In other words, does PG 9.0 supports cascading\nstandby configuration?\n\nThanks,\nIgor\n\nHi,Is it possible to use a standby instance as a master/primary for another standby in Postgres... |
[
{
"msg_contents": "I'm sorry.\n\n> Thank you for comments, this is revised version of the patch.\n\nThe malloc error handling in dblink.c of the patch is broken. It\nis leaking memory and breaking control.\n\ni'll re-send the properly fixed patch for dblink.c later.\n\n# This severe back pain should have made m... |
[
{
"msg_contents": "I'm sorry.\n\n> Thank you for comments, this is revised version of the patch.\n\nThe malloc error handling in dblink.c of the patch is broken. It\nis leaking memory and breaking control.\n\ni'll re-send the properly fixed patch for dblink.c later.\n\n# This severe back pain should have made m... |
[
{
"msg_contents": "Make group commit more effective.\n\nWhen a backend needs to flush the WAL, and someone else is already flushing\nthe WAL, wait until it releases the WALInsertLock and check if we still need\nto do the flush or if the other backend already did the work for us, before\nacquiring WALInsertLock.... |
[
{
"msg_contents": "Hello,\n\nYesterday I was facing a little issue with a backup software (NetBackup)\nthat do not report error when a post backup script is run. The problem\nis that this script execute pg_stop_backup() and if there's any failure\nPostgreSQL keeps running in on-line backup mode. So the backup i... |
[
{
"msg_contents": "Hello,\n\nI've run into a very odd issue calling C++ code that uses exceptions from within our PostgreSQL FDW. Specifically, we have broken our FDW into two components, a C layer that looks quite similar to the FDW for text files and a C++ layer that is called into by the C layer to interfac... |
[
{
"msg_contents": "On 23 November 2011 02:49, Robert Haas <robertmhaas@gmail.com> wrote:\n> There is no sort of systematic labeling of error messages in the log\n> to enable the DBA to figure out that the first error message is likely\n> nothing more serious than an integrity constraint doing its bit to\n> pres... |
[
{
"msg_contents": "Attached is a test case reduced from a real application. There is a\ntable with an index on a function written in PL/Python. There is a\nsecond PL/Python function that executes an INSERT into the table,\ncausing an index update. If the function used by the index fails, we\nget an error mes... |
[
{
"msg_contents": "Hello\n\nI looked to sources and I found a some useful routines for people who\nwrite extensions and probably PL too.\n\nThere are datum_compute_size and datum_write from range_types.c. These\nroutines can be used in PL libs and maybe in other places.\n\nShould be these routines moved to varl... |
[
{
"msg_contents": "Hi All,\n\nThis is regarding the TODO item :\n\"Add SPI_gettypmod() to return a field's typemod from a TupleDesc\"\n\nThe related message is:\nhttp://archives.postgresql.org/pgsql-hackers/2005-11/msg00250.php\n\nThis basically talks about having an SPI_gettypemod() which returns the\ntypmod o... |
[
{
"msg_contents": "At present log_newpage() produces log records called XLOG_HEAP_NEWPAGE.\n\nThat routine is used by HEAP, BTREE, GIN, SPGIST rmgrs, as well as\nvarious forks.\n\nWAL contains no information as to which rmgr the data refers to,\nmaking debugging much harder and skewing efforts to optimise WAL\n... |
[
{
"msg_contents": "\n\nHello,\n\nThis is my first patch review ever, so please bear with me.\n\nThe patch[1] is in the context diff format and applies cleanly to\ncurrent git HEAD. Documentation is updated by the patch.\n\nThe code does implement what's the patch is supposed to do.\n\nDo we want that? Accordi... |
[
{
"msg_contents": "freePGconn() does not free sslcompression. Fix.\n\nFound with valgrind.\n\n-- \nmarko",
"msg_date": "Wed, 1 Feb 2012 14:56:44 +0200",
"msg_from": "Marko Kreen <markokr@gmail.com>",
"msg_from_op": true,
"msg_subject": "libpq: fix sslcompression leak"
},
{
"msg_contents... |
[
{
"msg_contents": "The following bug has been logged on the website:\n\nBug reference: 6425\nLogged by: orval\nEmail address: postgres@dunquino.com\nPostgreSQL version: 9.0.6\nOperating system: Solaris 10 u9\nDescription: \n\nThis is intermittent and hard to reproduce but crashes con... |
[
{
"msg_contents": "Is spgist intended to support prefix searches with LIKE?\n\nI ask because, first, it seems like something spgist ought to be good\nat (unless I'm confused), and, second, the text_ops opfamily includes\nthese operators:\n\n~<~(text,text)\n ~<=~(text,text)\n ~>=~(text,text)\n ~>~(text,text)\n\n... |
[
{
"msg_contents": "\nI've just been running some timings of my JSON-producing functions, in \nparticular array_to_json, and comparing them with the current \nXML-producing functions. Here's a typical result:\n\n andrew=# explain analyse select array_to_json(array_agg(q),true)\n from (select * from pg_attr... |
[
{
"msg_contents": "Hi,\n\nI noticed that heap_tuple_needs_freeze might return true in cases where\nthe Xmax is leftover junk from somebody who set HEAP_XMAX_INVALID in the\nfar past without resetting the Xmax value itself to Invalid. I think\nthis is incorrect usage; the rule, I think, is that one shouldn't ev... |
[
{
"msg_contents": "\nSo freezing multixacts is not all that easy. I mean, you just scan the\npage looking for multis lesser than the cutoff; for those that are dead,\nthey can just be removed completely, but what about ones that still have\nmembers running? This is pretty unlikely but not impossible.\n\nIf th... |
[
{
"msg_contents": "In miracee's review of Peter's patch for new -A options in initdb (in\ncommitfest app only), it is noted that pg_hba.conf keyword parsing is\ndone in a case sensitive manner. So if you write \"Trust\" rather than\n\"trust\", it's not recognized.\n\nThis seemed pretty nonsensical to me, and i... |
[
{
"msg_contents": "Hey all,\n\nCould you tell me please an objective reason why PQunescapeBytea()\nreturns unsigned char* rather than just char* ?\nI am asking because a bit confused. How this intermixes with LO's API,\nwhich based on signed chars (although as we all know large object -\nis a just bytea splitte... |
[
{
"msg_contents": "I noticed ecpglib still uses PQconnectdb() with a craftily assembled\nconnection string. Here is a patch to use PQconnectdbParams() instead.",
"msg_date": "Thu, 02 Feb 2012 20:01:48 +0200",
"msg_from": "Peter Eisentraut <peter_e@gmx.net>",
"msg_from_op": true,
"msg_subject": ... |
[
{
"msg_contents": "On Thu, Feb 2, 2012 at 10:10 AM, Alvaro Herrera\n<alvherre@commandprompt.com> wrote:\n> Err, postgresql.conf processing is case insensitive, which is the most\n> closely related example. Β Are you saying we should make that case\n> sensitive as well? Β What I'm saying is that I see no good reas... |
[
{
"msg_contents": "Hi there,\n\nattached patch introduces NULLs indexing for SP-GiST. With this patch\nSp-GiST supports IS NULL, IS NOT NULL clauses, as well as full index scan.\n\nWe added boolean satisfyAll field in spgInnerConsistentIn and spgLeafConsistentIn \nstructures, which informs the user-defined met... |
[
{
"msg_contents": "I'm currently working with Duncan Rance's test case for bug #6425, and\nI am observing a very nasty behavior in HEAD: once one of the\nhot-standby query backends crashes, the standby postmaster SIGQUIT's\nall its children and then just quits itself, with no log message and\napparently no effo... |
[
{
"msg_contents": "If I run the following sequence of commands, I get an assertion\nfailure in current HEAD.\n\npostgres=# BEGIN;\nBEGIN\npostgres=# SELECT 1/0;\nERROR: division by zero\npostgres=# ROLLBACK TO A;\nERROR: no such savepoint\npostgres=# \\q\n\nThe process fails when the session is closed and abo... |
[
{
"msg_contents": "PostgreSQL 9.0.4:\n\nWhile bringing up a streaming replica, and while it is working its way through the WAL segments before connecting to the primary, I see a lot of messages of the form:\n\n2012-02-01 21:26:13.978 PST,,,24448,,4f2a1e61.5f80,54,,2012-02-01 21:25:53 PST,1/0,0,LOG,00000,\"resto... |
[
{
"msg_contents": "On Fri, Jan 27, 2012 at 8:35 AM, Heikki Linnakangas\n<heikki.linnakangas@enterprisedb.com> wrote:\n>> I think you should break this off into a new function,\n>> LWLockWaitUntilFree(), rather than treating it as a new LWLockMode.\n>> Also, instead of adding lwWaitOnly, I would suggest that we ... |
[
{
"msg_contents": "Robert Haas wrote:\n \n> A couple of things stand out at me from these graphs. First, some\n> of these transactions had really long latency. Second, there are a\n> remarkable number of seconds all of the test during which no\n> transactions at all manage to complete, sometimes several second... |
[
{
"msg_contents": "Tom Lane wrote:\n \n> More to the point, a GUC rollback transition *has to always\n> succeed*. Period.\n \nI was about to point out the exception of the transaction_read_only\nGUC, which according to the standard must not be changed except at\nthe beginning of a transaction or a subtransact... |
[
{
"msg_contents": "Tom Lane wrote:\n \n> What I was concerned about was the case where GUC is trying to\n> re-establish an old value during transaction rollback. For example,\n> assume we are superuser to start with, and we do\n> \n> begin;\n> set role unprivileged_user;\n> ...\n> rollback;\n> ... |
[
{
"msg_contents": "Tom Lane wrote:\n \n> Yeah, I think we need to preserve that property. Unexpectedly\n> executing query (which may have side-effects) is a very dangerous\n> thing. People are used to the idea that ANALYZE == execute, and\n> adding random other flags that also cause execution is going to\n> b... |
[
{
"msg_contents": "Consider this:\n\ncreate table arrays as select array[random(), random(), random(),\nrandom(), random(), random()] as a from generate_series(1, 1000000);\n\ncreate or replace function plpython_outputfunc() returns void as $$\nc = plpy.cursor('select a from arrays')\nfor row in c:\n pass\n$... |
[
{
"msg_contents": "While chasing a PL/Python memory leak, I did a few tests with PL/pgSQL\nand I think there are places where memory is not freed sufficiently early.\n\nAttached are two functions that when run will make the backend's memory\nconsumption increase until they finish. With both, the cause is\nconve... |
[
{
"msg_contents": "Pursuant to the recent discussion about bugs 6200 and 6245, I went\ntrawling through all the WAL redo routines looking for bugs such as\ninadequate locking or transiently trashing shared buffers. Here's\nwhat I found:\n\n* As we already knew, RestoreBkpBlocks is broken because it transiently... |
[
{
"msg_contents": "hiοΌ\nthere is a problem about type cast that i don't understand, follow is my test.\n \npostgres=# select 10::bit(3);\n bit\n-----\n 010\n(1 row)\npostgres=# select 10::bit varying(3);\nERROR: cannot cast type integer to bit varying\nLINE 1: select 10::bit varying(3);\n ^\npo... |
[
{
"msg_contents": "src/interfaces/libpq/fe-misc.c #include-s pg_config_paths.h, but in\nthe makefile that dependency is not declared.\n\nThis breaks the build with 'make -jN' (with a \"big\" N) ... sometimes\n(non-deterministically).\n\nPatch attached. Made from 9.1.1, but from browsing the git master on\nthe w... |
[
{
"msg_contents": "I have a rough proof-of-concept for getting nearest-neighbor searches \nworking with cubes. When I say \"rough\", I mean \"I have no idea what I'm \ndoing and I haven't written C for 15 years but I hear it got standardized \nplease don't hurt me\". It seems to be about 400x faster for a 3D ... |
[
{
"msg_contents": "Hi,\n\nWhen I compiled HEAD with --disable-integer-datetimes and tested\npg_receivexlog, I encountered unexpected replication timeout. As\nfar as I read the pg_receivexlog code, the cause of this problem is\nthat pg_receivexlog handles the standby message timeout incorrectly\nin --disable-int... |
[
{
"msg_contents": "Hello All,\n\n My application has to do a real time data upload to PostgreSQL\nserver. \n\n Every time i have to do a real time upload, i do not wish to open\nnew connection.\n I want to open a connection once [when my application comes up]\nand periodically chec... |
[
{
"msg_contents": "Hi,\n\nhttp://www.depesz.com/2012/02/03/waiting-for-9-2-pg_basebackup-from-slave/\n> =$ time pg_basebackup -D /home/pgdba/slave2/ -F p -x stream -c fast -P -v -h 127.0.0.1 -p 5921 -U replication\n> xlog start point: 2/AC4E2600\n> pg_basebackup: starting background WAL receiver\n> 692447/69244... |
[
{
"msg_contents": "Chetan Suttraway wrote:\n> Robert Haas wrote:\n \n>> Please add this to the next CommitFest:\n>>\n>> https://commitfest.postgresql.org/action/commitfest_view/open\n \n> At the given link, I am able to choose only \"System administration\"\n> under commitfest topic.\n> I think there has to b... |
[
{
"msg_contents": "\"Kevin Grittner\" wrote:\n \n> moved this to \"Replication and Recovery\"\n \nOh, that was a different patch -- I didn't see yours.\n \n(It's early, and the caffeine isn't working yet.)\n \nAnyway, you should have plenty of options now.\n \n-Kevin\n\n",
"msg_date": "Tue, 07 Feb 2012 06:... |
[
{
"msg_contents": "Hi,\n\nThis is regarding the TODO item:\n\"Prevent the specification of conflicting transaction read/write options\"\n\nlisted at:\nhttp://wiki.postgresql.org/wiki/Todo\n\nThe issue is :\n\nSET TRANSACTION read only read write read only;\n\nThe fix involved iteration over transaction_mode_lis... |
[
{
"msg_contents": "Recent events have made me notice the OID handling.\n\nAFAICS, OIDs are just a sequence with a max value that fits in a uint.\n\nSo ISTM that we should just strip out the OID handling code and just\nhave a system sequence defined like this\n\nCREATE SEQUENCE _pg_oid\n MINVALUE 0\n MAXVALU... |
[
{
"msg_contents": "[Posted at Andres's request]\n\nTL;DR: Inserting and indexing cubes is slow and/or broken in various ways in \nvarious builds.\n\nNOTABLE PROBLEMS\n\n1. In 9.1.2, inserting 10x rows takes 19x the time.\n - 9.1-HEAD and 9.2 \"fix\" this; it now slows down linearly\n - but: 10s > 8s > 5s!... |
[
{
"msg_contents": "Hi list,\n\nAndrew Dunstan reported an awkward-seeming case on IRC where shifting\naround a concatenation expression in a view made the planner choose a\ngood or a bad execution plan.\n\nSimplified, it boils down to this:\n\ndb=# create table foo(i int);\ndb=# explain verbose select i from (s... |
[
{
"msg_contents": "On Tue, Oct 25, 2011 at 7:37 PM, Magnus Hagander <magnus@hagander.net> wrote:\n> On Mon, Oct 24, 2011 at 14:40, Magnus Hagander <magnus@hagander.net> wrote:\n>> On Mon, Oct 24, 2011 at 13:46, Heikki Linnakangas\n>> <heikki.linnakangas@enterprisedb.com> wrote:\n>>> How does this interact with ... |
[
{
"msg_contents": "Add new keywords SNAPSHOT and TYPES to the keyword list in gram.y\n\nThese were added to kwlist.h as unreserved keywords in separate patches,\nbut authors forgot to add them to the corresponding list in gram.y.\nBecause of that, even though they were supposed to be unreserved keywords,\nthey ... |
[
{
"msg_contents": "Hi,\n\nwe have a database that is storing strings in various encodings (and\nnon-encodings, namely the arbitrary byte soup that you might see in\nemail headers from the internet). For this reason, the database uses\nsql_ascii encoding. The columns are text, as most characters are\nascii, so b... |
[
{
"msg_contents": "On a development system which wasn't being monitored very closely\nI think we've uncovered a bug in the listen/notify behavior. The\nsystem was struggling with lack of disk space for about a week\nbefore this surfaced, so it's probably not the most critical sort\nof bug we could have, but it... |
[
{
"msg_contents": "When Heikki worked up his original index-only scan patches (which\ndidn't end up looking much like what eventually got committed), he had\nthe notion of an index-only qual. That is, given a query like this:\n\nselect sum(1) from foo where substring(a,1,3) = 'abc';\n\nWe could evaluate the su... |
[
{
"msg_contents": "In his blog entry http://www.depesz.com/2011/07/08/wish-list-for-psql/\ndepesz described a simple way to do tab completion for SELECT in psql:\n\n\"\"\"\nMake tab-completion complete also function names β like: SELECT\npg_get<tab><tab> to see all functions that start with pg_get.\n\nMake tab-... |
[
{
"msg_contents": "Hi!\n\nI've always been a little wary of using the TRUNCATE command due to\nthe warning in the documentation about it not being \"MVCC-safe\":\nqueries may silently give wrong results and it's hard to tell when\nthey are affected.\n\nThat got me thinking, why can't we handle this like a stand... |
[
{
"msg_contents": "Attached is a proposed patch to deal with the issue described here:\nhttp://archives.postgresql.org/pgsql-bugs/2012-02/msg00000.php\n\nEven though we'd previously realized that comparing the text of\ninherited CHECK expressions is an entirely unsafe way to detect\nexpression equivalence (cf c... |
[
{
"msg_contents": "In view of the recently fixed data-corruption issues in hot standby\noperation (bugs 6200, 6425), the core team feels we should push out back\nbranch update releases soon. Due to unavailability of some key people,\nthe earliest feasible schedule turns out to be wrap Thursday 2/23 for\npublic... |
[
{
"msg_contents": "Dear hackers,\n\nThanks for the work on PLPython result metadata, it is very useful! I\njust came across a crash when trying to access this metadata on the\nresult of an UPDATE, which obviously cannot return any tuple (unless\nyou specify a RETURNING clause maybe?).\n\nPlease find attached a... |
[
{
"msg_contents": "The auto_explain module appears to create invalid JSON (in all versions\nsince 9.0). For example, with the settings\n\nauto_explain.log_format = 'json'\nauto_explain.log_min_duration = 0\n\nthe query\n\nselect * from pg_type;\n\nproduces this in the log:\n\nLOG: duration: 529.808 ms plan:\... |
[
{
"msg_contents": "I wonder if somewhere in Postgres source \"we\" are relying on the GCC \n\"correct behaviour\" regarding the read-modify-write of bitfield in\nstructures.\n\nTake a read at this https://lwn.net/Articles/478657/\n\nsorry if this was already mentioned.\n\n\nRegards\nGaetano Mendola\n",
"msg... |
[
{
"msg_contents": "\"Kevin Grittner\" wrote:\nTom Lane wrote:\n \n>> I agree it's a bug that you can do what Kevin's example shows.\n> \n> I'll look at it and see if I can pull together a patch.\n \nAttached.\n \nBasically, if a GUC has a check function, this patch causes it to be\nrun on a RESET just like it ... |
[
{
"msg_contents": "I decided to take a crack at the todo item created from the following post:\nhttp://archives.postgresql.org/pgsql-performance/2005-10/msg00458.php\n\nThe attached patch makes the desired changes in both code and function\nnaming.\n\nIt seemed quite easy to do but wasn't marked as easy on the ... |
[
{
"msg_contents": "Hackers, \n\nNTT Open Source has requested that I convene the 3rd Cluster Hackers summit at pgCon this year. As last year, it will be held on Tuesday (May 15th) during tutorials (and not conflicting with the Developer Summit).\n\nIf you are a contributor to any of PostgreSQL's various replic... |
[
{
"msg_contents": "Hackers,\n\nIn PL/pgSQL exception handling, I'm able to access the error code (SQLSTATE) and error message (SQLERRM). Is there any way to get at error details (yet)? If not, could SQLDETAIL or some such be added?\n\nThanks,\n\nDavid",
"msg_date": "Mon, 13 Feb 2012 09:27:16 -0800",
"ms... |
[
{
"msg_contents": "I have heard complaints that /contrib/pg_test_fsync is too slow. I\nthought it was impossible to speed up pg_test_fsync without reducing its\naccuracy.\n\nHowever, now that I some consumer-grade SATA 2 drives, I noticed that\nthe slowness is really in the open_sync test:\n\n\tCompare open_sy... |
[
{
"msg_contents": "Looking over the SSI 2PC code recently, I noticed that I overlooked a\ncase that could lead to non-serializable behavior after a crash.\n\nWhen we PREPARE a serializable transaction, we store part of the\nSERIALIZABLEXACT in the statefile (in addition to the list of SIREAD\nlocks). One of the... |
[
{
"msg_contents": "Last year at this time, I was investigating things like ext3 vs xfs, how \nwell Linux's dirty_bytes parameter worked, and how effective a couple of \npatches were on throughput & latency. The only patch that ended up \napplied for 9.1 was for fsync compaction. That was measurably better in ... |
[
{
"msg_contents": "Hi,\n\nI am checking a performance problem encountered after porting old embeded\nDB to postgreSQL. While the system is real-time sensitive, we are\nconcerning for per-query cost. In our environment sequential scanning\n(select * from ...) for a table with tens of thousands of record costs 1 ... |
[
{
"msg_contents": "I just noticed that we use the same gettext domain for all messages \nattached to one error. That is wrong in case of context information, \nwhere you have a stack of context lines, originating from different \nmodules. The result is that context lines don't always get translated.\n\nFor exam... |
[
{
"msg_contents": "diff --git a/doc/src/sgml/sepgsql.sgml b/doc/src/sgml/sepgsql.sgml\nindex e45c258..ee0a255 100644\n*** a/doc/src/sgml/sepgsql.sgml\n--- b/doc/src/sgml/sepgsql.sgml\n*************** UPDATE t1 SET x = 2, y = md5sum(y) WHERE\n*** 358,364 ****\n </synopsis>\n \n In this case we must have <... |
[
{
"msg_contents": "Hello\n\nI encountered a bug which always causes PostgreSQL to crash on Windows. \nAttached is a patch that fixes it. Please review it and include it in the \nupcoming minor releases of supported versions.\n\nThe following is a bug report.\n\n\nYour name :MauMau\nYour email address :maumau30... |
[
{
"msg_contents": "Speed up in-memory tuplesorting.\n\nPer recent work by Peter Geoghegan, it's significantly faster to\ntuplesort on a single sortkey if ApplySortComparator is inlined into\nquicksort rather reached via a function pointer. It's also faster\nin general to have a version of quicksort which is sp... |
[
{
"msg_contents": "pg_upgrade prints something like this:\n\nRestoring user relation files\n /var/lib/postgresql/8.4/main/base/35338/37229\n\nBut it's not actually \"restoring\" anything, is it?\n\nMaybe \"transferring\" would be better? (Or copying/linking, to be more\nprecise.)\n\n",
"msg_date": "Wed, 1... |
[
{
"msg_contents": "As per http://archives.postgresql.org/pgsql-general/2012-02/msg00304.php\nthere is no switch case in shdepReassignOwned for foreign data wrappers.\n\nThe obvious short-term answer (and probably the only back-patchable one)\nis to add a case for that object type. But after all the refactoring... |
[
{
"msg_contents": "On Sat, Feb 11, 2012 at 1:36 PM, Kevin Grittner\n<Kevin.Grittner@wicourts.gov> wrote:\n> \"Kevin Grittner\" Β wrote:\n> Tom Lane wrote:\n>\n>>> I agree it's a bug that you can do what Kevin's example shows.\n>>\n>> I'll look at it and see if I can pull together a patch.\n>\n> Attached.\n>\n> B... |
[
{
"msg_contents": "\non 2010-11-24 at 15:56, Tom Lane wrote:\n\n> Bug #5766 points out that we're still not there yet in terms of having\n> sane behavior for locale-specific regex operations in Unicode\n> encoding. The reason it's not working is that regc_locale does this to\n> expand the set of characters that... |
[
{
"msg_contents": "[Preamble: I've been told that the hackers list is appropriate for \nextension-related topics like this, even if it's not about contributing to \ncore. If I'm misappropriating, please let me know.]\n\nGoal: Personalized, context-relevant query results\n\nWe are building a deeply personalized ... |
[
{
"msg_contents": "Hackers,\n\nThe call is now open for Google Summer of Code.\n\nIf you are interested in being a GSoC mentor this summer, please reply\nto this email. I want to gauge whether or not we should participate\nthis summer.\n\n-- \nJosh Berkus\nPostgreSQL Experts Inc.\nhttp://pgexperts.com\n",
... |
[
{
"msg_contents": "In bug #6457 it's pointed out that we *still* don't have full\nfunctionality for locale-dependent regexp behavior with UTF8 encoding.\nThe reason is that there's old crufty code in regc_locale.c that only\nconsiders character codes up to 255 when searching for characters that\nshould be consi... |
[
{
"msg_contents": "Hello, sorry for long absense.\n\nAs far as I see, on an out-of-memory in getAnotherTuple() makes\nconn->result->resultStatus = PGRES_FATAL_ERROR and\nqpParseInputp[23]() skips succeeding 'D' messages consequently.\n\nWhen exception raised within row processor, pg_conn->inCursor\nalways posit... |
[
{
"msg_contents": "Hi!\n\nOleg and me found an incorrect behaviour when using a GiST index on points.\nIt's quite easy to reproduce.\n\ntest=# create table test as values (0,0.0000001);\ntest=# insert into test values (0,0.0000001);\ntest=# select * from test where point(x,y) <@ box(point(0,0),point(0,0));\n x ... |
[
{
"msg_contents": "When running Postgres on a single ext3 filesystem on Linux, we find that\nthe attached simple patch gives significant performance benefit (7-8% in\nnumbers below). The patch adds a new option for wal_sync_method, which\nis \"open_direct\". With this option, the WAL is always opened with\nO_... |
[
{
"msg_contents": "A while ago I went looking for nice ways to export an unencoded bytea \nvalue using psql, see \n<http://people.planetpostgresql.org/andrew/index.php?/archives/196-Clever-trick-challenge.html>. \nRegina Obe is also in want of a solution for this: \n<http://www.postgresonline.com/journal/archiv... |
[
{
"msg_contents": "Attached is a revision of the pg_stat_statements normalisation patch,\nplus its Python/psycopg2/dellstore2 test suite, which has yet to be\nconverted to produce pg_regress output. This revision is a response to\nthe last round of feedback given by reviewers. Highlights include:\n\n* No more i... |
[
{
"msg_contents": "Hi,\n\nOn a french PostgreSQL web forum, one of our users asked about a curious\nbehaviour of the intarray extension.\n\nThis query:\n SELECT ARRAY[-1,3,1] & ARRAY[1, 2];\nshould give {1} as a result.\n\nBut, on HEAD (and according to his tests, on 9.0.6 and 9.1.2), it\nappears to give en em... |
[
{
"msg_contents": "I looked into the complaint here of poor estimation for GIN indexscans:\nhttp://archives.postgresql.org/pgsql-performance/2012-02/msg00028.php\nAt first glance it sounds like a mistake in selectivity estimation,\nbut it isn't: the rowcount estimates are pretty nearly dead on.\nThe problem is ... |
[
{
"msg_contents": "In MySQL the below query is executing properly.\n\nSELECT * FROM <Table-name> WHERE (Table.ID LIKE '1%')\n\nBut when i try to execute the above query in Postgres, i get the following\nException \"org.postgresql.util.PSQLException: ERROR: operator does not\nexist: integer ~~ unknown Hint: No o... |
[
{
"msg_contents": "Hi,\n\nThis may have already been discussed before, but I can't find any\nmention of it. Would it be desirable to add support for triggers that\ncontain their own anonymous functions (i.e. DO)?\n\nSo instead of\n\nCREATE TRIGGER...\nEXECUTE PROCEDURE functioname();\n\nyou'd have:\n\nCREATE T... |
[
{
"msg_contents": "I'm basing an extension off contrib/cube. I'm going to open-source it under \nthe existing PostgreSQL license, but I'm not sure how the copyright notice \nshould look - there isn't one at the moment. (In fact, there's no LICENSE or \nCOPYRIGHT file at all.)\n\nShould it be something like\n\nP... |
[
{
"msg_contents": "Hi all,\n\nIs the following code well formed?\n\noldContext = MemoryContextSwitchTo(newContext);\n....\nif (something_bad) {\n elog(ERROR, ...);\n}\n...\nMemoryContextSwitchTo(oldContext);\n\n\nor do I have to ripristinate the oldContext before to issue the elog ?\n\n\n\nRegards\nGaetano Me... |
[
{
"msg_contents": "I figured it would be good if pg_regress reported its application_name\nas \"pg_regress\" rather than \"psql\". Any objections to the attached\npatch?",
"msg_date": "Sat, 18 Feb 2012 12:47:23 +0200",
"msg_from": "Peter Eisentraut <peter_e@gmx.net>",
"msg_from_op": true,
"msg_... |
[
{
"msg_contents": "Can anybody with a win64 build reproduce the misbehavior reported in bug\n#6460? I'm not currently interested in the question of whether my_log2\nought to be changed --- the question rather is why is the system not\nnoticing that his shared_buffers value overflows size_t.\n\n\t\t\tregards, t... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.