Skip site navigation (1) Skip section navigation (2)

Re: VACUUM FULL deadlock with backend startup

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: VACUUM FULL deadlock with backend startup
Date: 2011-03-19 13:45:10
Message-ID: AANLkTinUbjbA5rB3Qb0k87DAJyaq08fGV9W=4Nv8DMRj@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Fri, Mar 18, 2011 at 11:25 PM, Nikhil Sontakke
<nikhil(dot)sontakke(at)enterprisedb(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2011-03-19 14:01:44
Subject: Re: pg_last_xact_replay_timestamp meaning
Previous:From: Magnus HaganderDate: 2011-03-19 13:14:18
Subject: Re: Indent authentication overloading

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group