[HACKERS] Apprentices? (was =patch - Report the schema...)

, because of temperament or work style, but I'm sure some are. Might this help? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Range types

that work is if we specify a scale for timestamptz, and that strikes me as a big change to its semantics. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [HACKERS] [GENERAL] contrib/plantuner - enable PostgreSQL planner hints

On Oct 16, 2009, at 10:04 AM, decibel wrote: Out of curiosity, did you look at doing hints as comments in a query? I don't think that a contrib module could change the grammar. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

[HACKERS] Proposal: String key space for advisory locks

in advance for any comments. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Proposal: String key space for advisory locks

On Oct 26, 2009, at 5:24 PM, Itagaki Takahiro wrote: Hmmm, hashtext() returns int32. , Can you reduce the collision issue if we had hashtext64()? That would certainly reduce the chance of a collison considerably, assuming the right algorithm. -- -- Christophe Pettus x...@thebuild.com

Re: [HACKERS] Proposal: String key space for advisory locks

-designed hashtext64() would help a lot. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] xlog min recovery request ... is past current point ...

connected to the primary without issue, so: Are these messages something to be concerned over? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] hstores in pl/python

from the problem that it needs to sniff the hstore OID, which is somewhat annoying, especially in a web environment where the sniff has to happen repeatedly. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes

Re: [HACKERS] Why don't we accept exponential format for integers?

Python 2.6.1 (r261:67515, Jun 24 2010, 21:47:49) [GCC 4.2.1 (Apple Inc. build 5646)] on darwin Type help, copyright, credits or license for more information. isinstance(10,int) True isinstance(1e10,int) False -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing

Re: [HACKERS] and it's not a bunny rabbit, either

. Thanks, computer program: Swerved off road, hit tree is about as useful. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

[HACKERS] Logging both start and end of temporary file usage

). If this sounds like something worthwhile in general, I can package it up as a proper patch. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] pg_rewind, a tool for resynchronizing an old master after failover

of the Django license and copyright notice. (I don't have my copy right in front of me, but I don't think it's a full-on assignment of copyright.) -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] Final(?) proposal for wal_sync_method changes

On Dec 7, 2010, at 2:43 PM, Josh Berkus wrote: Because nobody sane uses OSX on the server? The XServe running 10.5 server and 9.0.1 at the other end of the office takes your remark personally. :) -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql

[HACKERS] ereport documentation patch

Is it reasonable to note in the documentation that ereport does not return if the error severity is greater than or equal to ERROR? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] ereport documentation patch

On Aug 19, 2013, at 11:28 PM, Heikki Linnakangas wrote: On 19.08.2013 23:40, Christophe Pettus wrote: Is it reasonable to note in the documentation that ereport does not return if the error severity is greater than or equal to ERROR? Yeah, it probably would be good to mention that. Got

[HACKERS] Getting the clog bits for a particular xid

, or the 943470*2 = 1886940th bit. So, (counting from the MSB being 0), it's the 4th and 5th bit of byte offset 235867 in that file. Is that correct? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

[HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

. No errors in the log files on either system. -- Obviously, we're very concerned that a bug was introduced in the latest minor release. We're happy to gather data as required to assist in diagnosing this. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

On Nov 18, 2013, at 10:58 AM, Christophe Pettus x...@thebuild.com wrote: As a note, P1 was created from another system (let's call it P0) using just WAL shipping (no streaming replication), and no data corruption was observed. As another data point, P0 was running 9.0.13, rather than 9.0.14

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

. 5. PostgreSQL recovers normally (pulling a small number of WAL segments from WAL-E), and eventually connects to P2. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

conninfo? Correct. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

elsewhere. 2. P1 never had hot_standby = 'on', as it was never intended to be a hot stand_by. 3. S1 did have hot_standby = 'on. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

On Nov 18, 2013, at 11:47 AM, Andres Freund and...@2ndquadrant.com wrote: Without deleting any data, including pg_xlog/, backup.label, anything? One more correction: After rsync finished and the pg_base_backup() was issued, the contents of pg_xlog/ on S1 were deleted. -- -- Christophe Pettus

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

On Nov 18, 2013, at 12:00 PM, Christophe Pettus x...@thebuild.com wrote: One more correction: After rsync finished and the pg_base_backup() was issued, the contents of pg_xlog/ on S1 were deleted. pg_stop_backup(), sorry. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

workload. The P1/P2 client has a very high level of writes; the P3 more read-heavy, but still a fair number of writes. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

(pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

On Nov 18, 2013, at 2:26 PM, Andres Freund and...@2ndquadrant.com wrote: Trying to reproduce the issue with and without hot_standby=on would be very helpful, but I guess that's time consuming? I've been working on it, but I haven't gotten it to fail yet. I'll keep at it. -- -- Christophe

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

it. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

now is that we have an unknown number of silently corrupt secondaries out there which will only be discovered when someone promotes them to being a primary (possibly because the current primary died without a backup), I'd say that this is something pretty urgent. -- -- Christophe Pettus x

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

. What concerns me more is that we don't seem to have a framework to put in a regression test on the bug you just found (and thank you for finding it so quickly!). -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

On Nov 19, 2013, at 10:51 AM, Andres Freund and...@2ndquadrant.com wrote: You seem to imply that I/we should do that work? No, just that it be done. Of course, the more support from the professional PG community that is given to it, the better. -- -- Christophe Pettus x...@thebuild.com

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

Hi, Andres, From my understanding, the problem only occurs over streaming replication; if the secondary was never a hot standby, and only used the archived WAL segments, that would be safe. Is that correct? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list

Re: [HACKERS] Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1

secondary running the affected versions which is started with hot_standby=on could potentially be corrupted even if it never connects to a primary? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

[HACKERS] stuck spinlock

/Linux. Generally, there's no core file (which is currently enable), as the postmaster just normally exits the backend. Diagnosis suggestions? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription

Re: [HACKERS] stuck spinlock

/mit-krb5 -L/usr/lib/x86_64-linux-gnu/mit-krb5 -L/usr/lib/x86_64-linux-gnu -Wl,--as-needed LDFLAGS_EX = LDFLAGS_SL = LIBS = -lpgport -lpgcommon -lxslt -lxml2 -lpam -lssl -lcrypto -lkrb5 -lcom_err -lgssapi_krb5 -lz -ledit -lcrypt -ldl -lm VERSION = PostgreSQL 9.3.2 -- -- Christophe Pettus x

Re: [HACKERS] stuck spinlock

concurrent? Standby? ... The workload is not very highly concurrent; actually quite lightly loaded. There are a very large number (442,000) of user tables. No standby attached. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org

Re: [HACKERS] stuck spinlock

. The server was running with shared_buffers=100GB, but the problem has reoccurred now with shared_buffers=16GB. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

Re: [HACKERS] stuck spinlock

0x7f699c742960 in PostgresMain () #20 0x7f699c6ff765 in PostmasterMain () #21 0x7f699c53bea2 in main () -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql

Re: [HACKERS] stuck spinlock

:196 -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] stuck spinlock

=0x7fa0425e91a0) at /tmp/buildd/postgresql-9.3-9.3.2/build/../src/backend/main/main.c:196 -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] stuck spinlock

on multiple machines, so it's unlikely to be hardware) is that there are a relatively large number of relations (like, 440,000+) distributed over many schemas. Is there anything that pins a buffer that is O(N) to the number of relations? -- -- Christophe Pettus x...@thebuild.com -- Sent

Re: [HACKERS] stuck spinlock

On Dec 12, 2013, at 6:15 PM, Tom Lane t...@sss.pgh.pa.us wrote: Are you possibly using any nonstandard extensions? No, totally stock PostgreSQL. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] stuck spinlock

0.00 0.00 11.003.00 0.22 0.1249.14 0.000.000.000.00 0.00 0.00 sdd 0.00 0.000.000.00 0.00 0.00 0.00 0.000.000.000.00 0.00 0.00 -- -- Christophe Pettus x...@thebuild.com -- Sent via

Re: [HACKERS] stuck spinlock

--- 0 (1 row) -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] stuck spinlock

, rather than specifically related to the spinlock issue. What this does reveal is that all the spinlock issues have been on long-running queries, for what it is worth. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make

Re: [HACKERS] stuck spinlock

was experiencing this.) -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] stuck spinlock

to facilities like statement_timeout or lock_timeout that cancel a query asynchronously. I assume pg_cancel_backend() would apply as well. We've only seen it on one client, and that client had a *lot* (thousands on thousands) of statement_timeout cancellations. -- -- Christophe Pettus x

Re: [HACKERS] stuck spinlock

On Dec 13, 2013, at 8:52 AM, Tom Lane t...@sss.pgh.pa.us wrote: Please apply commit 478af9b79770da43a2d89fcc5872d09a2d8731f8 and see if that doesn't fix it for you. It appears to fix it. Thanks! -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql

[HACKERS] Streaming replication bug in 9.3.2, WAL contains references to invalid pages

can provide. Best, -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

, in particular, does not have stable field order. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

were starting over, we wouldn't start by creating our own proprietary hierarchical type and then making the hierarchical type everyone else uses depend on it. hstore exists because json didn't. But json does now, and we shouldn't create a jsonb dependency on hstore. -- -- Christophe Pettus

Re: [HACKERS] jsonb and nested hstore

|| jsonb (and likely the other combinatorics of json and jsonb), along with the appropriate GIN and GiST interfaces for jsonb. Why would that not work? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your

Re: [HACKERS] jsonb and nested hstore

On Feb 27, 2014, at 8:31 PM, Peter Geoghegan p...@heroku.com wrote: On Thu, Feb 27, 2014 at 8:23 PM, Christophe Pettus x...@thebuild.com wrote: Surely, the answer is to define a jsonb || jsonb (and likely the other combinatorics of json and jsonb), along with the appropriate GIN and GiST

Re: [HACKERS] jsonb and nested hstore

On Feb 27, 2014, at 9:12 PM, Craig Ringer cr...@2ndquadrant.com wrote: On 02/28/2014 12:43 PM, Christophe Pettus wrote: My proposal is that we break the dependencies of jsonb (at least, at the user-visible level) on hstore2, thus allowing it in core successfully. jsonb || jsonb returning

Re: [HACKERS] jsonb and nested hstore

. There are missing operators, yes; that's a very straight-forward hole to plug. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

there are people who don't like the idea, and I get that. But I don't see the basis for the dislike. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

consensus by reaching a compromise that weighs everyone's concerns. The thing I still haven't heard is why jsonb in core is a bad idea, except that it is too much code. Is that the objection? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

it into this patch) can be added over time. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

they don't get to pick what packages are installed on their server (RDS, for example). Telling them that something is in -contrib can very well be telling them You can't have it in those cases. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

don't initially have indexing operations for it. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

On Feb 28, 2014, at 1:34 PM, Peter Geoghegan p...@heroku.com wrote: Amazon RDS Postgres has hstore. Just observing that putting something in -contrib does not mean every installation can automatically adopt it. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers

Re: [HACKERS] jsonb and nested hstore

. To put it mildly, there's no consensus on that point; indeed, I think there's consensus that's a non-starter. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

[HACKERS] Deciding which index to use

Where in the optimizer code does PostgreSQL decide which of several possibly-matching partial indexes to use? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org

[HACKERS] HashAggregate row estimate = 200

? -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] Alter or rename enum value

ry brutal solution like marking indexes containing the altered type invalid on a ROLLBACK would be preferable to the current situation. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscript

Re: [HACKERS] Alter or rename enum value

erting a new enum value, then populating a dimension table for it) would have to be done as two migrations rather than one, but that is much more doable in most tools than having a migration run without a transaction at all. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hac

Re: [HACKERS] Alter or rename enum value

an enum type to which a value was added, and the transaction was rolled back? For the 90% use case, that would be acceptable, I would expect. -- -- Christophe Pettus x...@thebuild.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscr

Re: [HACKERS] [COMMITTERS] pgsql: Implement table partitioning.

> On Dec 9, 2016, at 22:52, Keith Fiske wrote: > On Fri, Dec 9, 2016 at 10:01 PM, Robert Haas wrote: >> One thing that's tricky/annoying about this is that if you have a >> DEFAULT partition and then add a partition, you have to scan the >> DEFAULT

Re: [HACKERS] [BUGS] BUG #14825: enum type: unsafe use?

> On Sep 25, 2017, at 07:55, Andrew Dunstan > wrote: > Let's ask a couple of users who I think are or have been actually > hurting on this point. Christophe and David, any opinions? Since about 90% of what I encounter in this area are automatically-generated