Re: VACUUM FULL deadlock with backend startup

Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>

From: Nikhil Sontakke <nikhil.sontakke@enterprisedb.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2011-03-19T14:46:48Z
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