Re: Hung Vacuum in 8.3 - Mailing list pgsql-bugs

From Greg Stark
Subject Re: Hung Vacuum in 8.3
Date
Msg-id AANLkTi=L2tGGVU25s-190xggura=rm8RmKgkA6S0NbTw@mail.gmail.com
Whole thread Raw
In response to Re: Hung Vacuum in 8.3  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
List pgsql-bugs
On Mon, Mar 7, 2011 at 11:55 PM, Mark Kirkwood
<mark.kirkwood@catalyst.net.nz> wrote:
> =A0stuff =A0 | =A0 23957 | 2011-03-08 06:02:02.659159+13 | VACUUM ANALYZE;
>

For what it's worth VACUUM ANALYZE does have to take an additional
lock to update the statistics. It should rarely cause any problems but
it is a possibility.

When you do get a good example you might want to take the contents of
pg_locks at the same time as pg_stat_activity. That would at least be
able to help rule out any real locks and make it clear it's really
stuck on waiting for a block to become unpinned.

--=20
greg

pgsql-bugs by date:

Previous
From: Mark Kirkwood
Date:
Subject: Re: Hung Vacuum in 8.3
Next
From: Mark Kirkwood
Date:
Subject: Re: Hung Vacuum in 8.3