Postgres Pro
Downloads
Home   >   mailing lists

Re: unlink for DROPs after releasing locks (was Re: Should I implement DROP INDEX CONCURRENTLY?) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: unlink for DROPs after releasing locks (was Re: Should I implement DROP INDEX CONCURRENTLY?)
Date
Msg-id 7743.1339685140@sss.pgh.pa.us
Whole thread Raw
In response to Re: unlink for DROPs after releasing locks (was Re: Should I implement DROP INDEX CONCURRENTLY?)  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: unlink for DROPs after releasing locks (was Re: Should I implement DROP INDEX CONCURRENTLY?)
List pgsql-hackers
Tree view 
Robert Haas <robertmhaas@gmail.com> writes:
> Is RESOURCE_RELEASE_AFTER_LOCKS actually used for anything?  Is it
> just for extensions?

I'm too lazy to go look, but it certainly ought to be in use.
The idea is that that's the phase for post-lock-release cleanup,
and anything that can possibly be postponed till after releasing
locks certainly should be ...
        regards, tom lane

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Backup docs
Next
From: Phil Sorber
Date:
Subject: Re: libpq compression