| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Hung Vacuum in 8.3 |
| Date: | 2011-03-08 01:57:14 |
| Message-ID: | AANLkTi=L2tGGVU25s-190xggura=rm8RmKgkA6S0NbTw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Mar 7, 2011 at 11:55 PM, Mark Kirkwood
<mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> wrote:
> stuff | 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.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Allan E. Registos | 2011-03-08 02:23:21 | Re: BUG #5916: PGAdmin crash |
| Previous Message | Jacob Lee | 2011-03-08 01:32:16 | BUG #5919: released zipped files have problem |