RE: Good name for new lock type for VACUUM?
Hiroshi Inoue <inoue@tpf.co.jp>
From: "Hiroshi Inoue" <Inoue@tpf.co.jp>
To: "Tom Lane" <tgl@sss.pgh.pa.us>, "Peter Eisentraut" <peter_e@gmx.net>
Cc: <pgsql-hackers@postgreSQL.org>
Date: 2001-06-23T14:39:39Z
Lists: pgsql-hackers
> -----Original Message----- > From: Hiroshi Inoue > > -----Original Message----- > > From: Tom Lane > > > > Peter Eisentraut <peter_e@gmx.net> writes: > > > 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. > > > > Okay with me, unless someone else comes up with a better idea... > > > > I have no better idea but I hope to leave VacuumLock as an alias > because I can't remember others. > Isn't it a better idea to have a separate 'SELF EXCLUSIVE' lock which conflicts with only itself ? regards, HIroshi Inoue