Re: "multiple backends attempting to wait for pincount 1" - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: "multiple backends attempting to wait for pincount 1"
Date
Msg-id 54EAC2B1.2060802@kaltenbrunner.cc
Whole thread Raw
In response to "multiple backends attempting to wait for pincount 1"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 02/13/2015 06:27 AM, Tom Lane wrote:
> Two different CLOBBER_CACHE_ALWAYS critters recently reported exactly
> the same failure pattern on HEAD:
> 
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=markhor&dt=2015-02-06%2011%3A59%3A59
> http://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=tick&dt=2015-02-12%2010%3A22%3A57
> 
> I'd say we have a problem.  I'd even go so far as to say that somebody has
> completely broken locking, because this looks like autovacuum and manual
> vacuuming are hitting the same table at the same time.

fwiw - looks like spoonbill(not doing CLOBBER_CACHE_ALWAYS) managed to
trigger that ones as well:

http://www.pgbuildfarm.org/cgi-bin/show_log.pl?nm=spoonbill&dt=2015-02-23%2000%3A00%3A06

there is also some failures from the BETWEEN changes in that
regression.diff but that might be fallout from the above problem.


Stefan



pgsql-hackers by date:

Previous
From: Corey Huinker
Date:
Subject: Re: dblink: add polymorphic functions.
Next
From: Venkata Balaji N
Date:
Subject: Re: Redesigning checkpoint_segments