From: | "Steven Flatt" <steven(dot)flatt(at)gmail(dot)com> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #3883: Autovacuum deadlock with truncate? |
Date: | 2008-01-17 19:11:10 |
Message-ID: | 357fa7590801171111m707f69c9nab445278b266d054@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 1/17/08, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > This isn't a postgres deadlock per se, but the end result is that two
> > postgres backends are stuck, each waiting on a PGSemaphoreLock that the
> > other presumably has. The processes have been stuck for hours.
>
> Can you reproduce this problem at will?
Well we have a bunch of test runs (at least a few dozen) that do a
similar thing, but only this one seems to be stuck. Still, I imagine
I can reproduce by doing enough updates/deletes to interest the
autovacuumer immediately followed by executing the fn_clean_tables()
function -- however not sure of the precise timing to get into this
state.
> Are the processes still running (sleeping, rather) so that we can try to
> examine them more deeply?
Yes, the processes are still "sleeping" in the same state. Just did
another bt a few minutes ago and they're the exact same. Don't
imagine the processes are going to be moving much...
Steve
From | Date | Subject | |
---|---|---|---|
Next Message | Steven Flatt | 2008-01-17 19:25:03 | Re: BUG #3883: Autovacuum deadlock with truncate? |
Previous Message | Tom Lane | 2008-01-17 18:27:46 | Re: BUG #3883: Autovacuum deadlock with truncate? |