Re: VACUUM FULL deadlock with backend startup

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: VACUUM FULL deadlock with backend startup
Дата
Msg-id AANLkTinUbjbA5rB3Qb0k87DAJyaq08fGV9W=4Nv8DMRj@mail.gmail.com
обсуждение исходный текст
Ответ на VACUUM FULL deadlock with backend startup  (Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>)
Ответы Re: VACUUM FULL deadlock with backend startup  (Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>)
Список pgsql-hackers
On Fri, Mar 18, 2011 at 11:25 PM, Nikhil Sontakke
<nikhil.sontakke@enterprisedb.com> wrote:
> The fix is similar to the earlier commit by Tom. I tested this fix
> against 8.3.13. We lock the parent catalog now before calling
> index_open. Patch against git HEAD attached with this mail. I guess we
> will backpatch this? Tom's last commit was backpatched till 8.2 I
> think.

Is it really worth slowing down the startup sequence for every
connection to avoid deadlocking against a very rare maintenance
operation?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: Indent authentication overloading
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: pg_last_xact_replay_timestamp meaning