Re: Lock pileup stuck processes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Lock pileup stuck processes
Date: 2016-04-13 23:06:29
Message-ID: 5284.1460588789@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Josh berkus <josh(at)agliodbs(dot)com> writes:
> Summary: in some cases, "lock pileups" fail to resolve completely, and
> one or more orphan backends are left in permanent lock-waiting state.
> ...
> My attempts to reproduce this issue under synthetic circumstances have
> not been successful. strace of the stuck backends shows no activity.

Please see if you can get a stack trace from a stuck backend.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message porjo38 2016-04-14 03:58:35 BUG #14083: 'postgresql95-setup initdb' breaks inside docker container
Previous Message Josh berkus 2016-04-13 22:59:44 Lock pileup stuck processes