Re: Good name for new lock type for VACUUM?

> Tom Lane writes:
> 
> > Awhile ago I said that I wanted to create a new flavor of table-level
> > lock for concurrent VACUUM to get on a table.
> 
> > I'm having a hard time coming up with a name, though.  I originally
> > called it "VacuumLock" but naming it after its primary use seems bogus.
> 
> Not that a name like "share row exclusive" is any less bogus. ;-)
> 
> I've been staring at the lock names for an hour now and the best name I've
> come up with is SHARE UPDATE EXCLUSIVE, as in "share update, otherwise
> exclusive" (the implication being that update would allow select as well),
> or some permutation thereof.
> 
> Any other constructs that follow the existing patterns lead to
> significantly less desirable names like
> 
> EXCLUSIVE ROW EXCLUSIVE == like ROW EXCLUSIVE, but self-exclusive, or
> 
> ROW EXCLUSIVE SHARE == like SHARE, but allows ROW EXCLUSIVE

Sounds good.  I documented the lock types as best I could in the LOCK
manual page.  I think that is as good as we can do to explain them.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026