AccessExclusiveLock with pg_locks.locktype of tuple

2019-12-18 Thread Erik Jones
found so far on them is this old pgsql-general thread wherein Tom Lane essentially just says, "Yeah, it can happen and is an implementation detail that can change from version to version." That was on 9.4.x and the my most recent confirmed sighting was on a server running 11.3. -- Erik

Re: Hot Standby Conflict on pg_attribute

2019-05-11 Thread Erik Jones
s setting > old_snapshot_threshold to any value at all besides zero. (On 12+ you can > directly control the truncation behavior.) > > -Jeremy > Thanks for the tip! -- Erik Jones mag...@gmail.com

Re: Hot Standby Conflict on pg_attribute

2019-05-10 Thread Erik Jones
On Fri, May 10, 2019 at 12:41 PM Tom Lane wrote: > Andres Freund writes: > > On 2019-05-09 13:03:50 -0700, Erik Jones wrote: > >> The question then is: Why would these user queries be waiting on an > >> AccessShare lock on pg_attribute? > > > Queries that

Re: Hot Standby Conflict on pg_attribute

2019-05-10 Thread Erik Jones
Hi Andres, Thank you very much! That's exactly what I needed. On Fri, May 10, 2019 at 12:14 PM Andres Freund wrote: > Hi, > > On 2019-05-09 13:03:50 -0700, Erik Jones wrote: > > The question then is: Why would these user queries be waiting on an > > AccessShare lock on pg

Hot Standby Conflict on pg_attribute

2019-05-09 Thread Erik Jones
are being sent as single query transactions via this Node.js postgres adapter: https://github.com/brianc/node-postgres which is pretty bare bones. -- Erik Jones mag...@gmail.com