Re: [HACKERS] [COMMITTERS] pgsql: Add amcheck extension to contrib.

2017-03-14 Thread Andres Freund
On 2017-03-13 14:09:39 -0700, Andres Freund wrote: > Hi, > > On 2017-03-13 15:45:01 -0400, Tom Lane wrote: > > I could be wrong, but the most obvious explanation for this failure is > > that autovacuum had a lock on the table or index when we looked. > > Even if that isn't why axolotl failed in th

Re: [HACKERS] [COMMITTERS] pgsql: Add amcheck extension to contrib.

2017-03-13 Thread Andres Freund
Hi, On 2017-03-13 15:45:01 -0400, Tom Lane wrote: > I could be wrong, but the most obvious explanation for this failure is > that autovacuum had a lock on the table or index when we looked. > Even if that isn't why axolotl failed in this particular case, I think > it's dead certain that we will se

Re: [HACKERS] [COMMITTERS] pgsql: Add amcheck extension to contrib.

2017-03-13 Thread Tom Lane
Andres Freund writes: > Add amcheck extension to contrib. axolotl just failed on this: https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=axolotl&dt=2017-03-13%2017%3A49%3A24 *** *** 78,86 -- make sure we don't have any leftover locks SELECT * FROM pg_locks WHERE rel