[GENERAL] 9.5 "chained equality" behavior

t see what in the 9.5 changelog (https://www.postgresql.org/docs/9.6/static/release-9-5.html) would cause this to syntax error. I'm worried that there are other incompatibilities that we didn't notice. Can anyone shed some light? -- Joshua Ma Benchling | benchling.com

Re: [GENERAL] Transaction lock granting order

Thanks a bunch Tom, appreciate the quick response. On Mon, Dec 5, 2016 at 12:33 PM, Tom Lane wrote: > Joshua Ma writes: > > Can someone point me to documentation on (or confirm) this detail on > > Postgres locking? > > > - Transaction X starts and acquires a lock on a t

[GENERAL] Transaction lock granting order

Can someone point me to documentation on (or confirm) this detail on Postgres locking? - Transaction X starts and acquires a lock on a table T - Transaction Y starts and attempts to acquire a conflicting lock on T - it is now blocked - Transaction Z starts and also attempts to acquire a conflictin

[GENERAL] pg_restore casts check constraints differently

This might not be a common case, but we're using pg_dump in a testing environment to check migrations - 1) we initialize the db from HEAD, pg_dump it, 2) we initialize the db from migration_base.sql, apply migrations, pg_dump it, and 3) compare the two dumps to verify that our migrations are correc

[GENERAL] Recommendations for migrating PG 9.3 RDS across regions

I'm currently looking into how we might migrate an AWS-hosted database (via RDS) from us-west-2 to us-east-1. This isn't natively supported by RDS right now, so I was wondering if anyone has had success with 3rd-party tools. (I'm also on 9.3, unfortunately, so I lack some of 9.4's replication featu

Re: [GENERAL] Why does CREATE INDEX CONCURRENTLY need two scans?

Ah, that's exactly what I was looking for. Thanks everyone for the responses! - Josh ᐧ On Tue, Mar 31, 2015 at 8:54 PM, Tom Lane wrote: > Michael Paquier writes: > > On Wed, Apr 1, 2015 at 9:43 AM, Joshua Ma wrote: > >> Why are two scans necessary? What would break i

Re: [GENERAL] Why does CREATE INDEX CONCURRENTLY need two scans?

e data gets inserted after the 1st snapshot, the 1st scan wouldn't pick anything up and the 3-step process I had earlier becomes identical to the 2-step process. Is there something special about index_build? - Josh On Tue, Mar 31, 2015 at 7:08 PM, Michael Paquier wrote: > > > On Wed,

[GENERAL] Why does CREATE INDEX CONCURRENTLY need two scans?

Hi all, I was curious about why CONCURRENTLY needs two scans to complete - from the documentation on HOT (access/heap/README.HOT), it looks like the process is: 1) insert pg_index entry, wait for relevant in-progress txns to finish (before marking index open for inserts, so HOT updates won't writ