Re: deadlock with vacuum full on 7.4.5
| От | Joseph Shraibman |
|---|---|
| Тема | Re: deadlock with vacuum full on 7.4.5 |
| Дата | |
| Msg-id | 416C6043.1080104@selectacast.net обсуждение исходный текст |
| Ответ на | Re: deadlock with vacuum full on 7.4.5 (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: deadlock with vacuum full on 7.4.5
|
| Список | pgsql-general |
Why then when I did a kill -INT on the vacuuming backends did everything unfreeze? Tom Lane wrote: > Joseph Shraibman <jks@selectacast.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
В списке pgsql-general по дате отправления: