| From: | Joseph Shraibman <jks(at)selectacast(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: deadlock with vacuum full on 7.4.5 |
| Date: | 2004-10-12 22:52:51 |
| Message-ID: | 416C6043.1080104@selectacast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Why then when I did a kill -INT on the vacuuming backends did everything
unfreeze?
Tom Lane wrote:
> Joseph Shraibman <jks(at)selectacast(dot)net> writes:
>
>>Last night one of these vacuum fulls deadlocked with a query on this
>>table. Both were stuck doing nothing until I did a kill -INT on the
>>backends doing the vacuum.
>
>
>>So my questions:
>>1) What can I do to avoid this?
>>2) What do I do next time this happens to get more debugging info out of
>>the situation?
>
>
> Look in pg_locks and pg_stat_activity.
>
> I think it is highly unlikely that there was a deadlock inside the
> database. Far more likely that both jobs were waiting on some
> idle-in-transaction client whose transaction was holding a lock
> on the table.
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-10-12 23:05:46 | Re: deadlock with vacuum full on 7.4.5 |
| Previous Message | Ted Shab | 2004-10-12 22:48:41 | LISTEN/NOTIFY for lightweight replication |