Re: VACUUM FULL deadlock with backend startup - Mailing list pgsql-hackers

From Nikhil Sontakke
Subject Re: VACUUM FULL deadlock with backend startup
Date
Msg-id AANLkTikjUFoTcCvFpfS4okptBKepfhMryYgMF=8VmYXT@mail.gmail.com
Whole thread
In response to Re: VACUUM FULL deadlock with backend startup  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: VACUUM FULL deadlock with backend startup
List 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

pgsql-hackers by date:

Previous
From: Yeb Havinga
Date:
Subject: Re: Sync Rep and shutdown Re: Sync Rep v19
Next
From: Tom Lane
Date:
Subject: Re: tolower() identifier downcasing versus multibyte encodings