Re: VACUUM FULL deadlock with backend startup

From: Nikhil Sontakke <nikhil(dot)sontakke(at)enterprisedb(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: VACUUM FULL deadlock with backend startup
Date: 2011-03-19 14:46:48
Message-ID: AANLkTikjUFoTcCvFpfS4okptBKepfhMryYgMF=8VmYXT@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

> 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?
>
>
Not really a performance issue AFAICS. If the relcache init file exists,
then the phase2 of the catalog cache which eventually calls the above code
path is avoided.

Regards,
Nikhils

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-03-19 15:05:41 Re: tolower() identifier downcasing versus multibyte encodings
Previous Message Yeb Havinga 2011-03-19 14:32:53 Re: Sync Rep and shutdown Re: Sync Rep v19