Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY
От | Jim C. Nasby |
---|---|
Тема | Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY |
Дата | |
Msg-id | 20030616061738.GE40542@flake.decibel.org обсуждение исходный текст |
Ответ на | Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY
Re: SELECT blocking on ALTER TABLE ADD FOREIGN KEY |
Список | pgsql-hackers |
On Thu, Jun 12, 2003 at 06:23:12PM -0400, Tom Lane wrote: > "Jim C. Nasby" <jim@nasby.net> writes: > > Is there any ALTER that would require blocking selects? > > DROP INDEX, for certain. Sure, but that's usually trivially fast. > > Even stuff like > > drop and rename should be protected by versioning, no? > > No. System-catalog changes are always READ COMMITTED mode. Yeah, so the catalog changes shouldn't be visible to anyone until after the ALTER is complete, right? Even if a transaction is set to read uncommitted, I assume it will always read only committed data from the catalogs... -- Jim C. Nasby (aka Decibel!) jim@nasby.net Member: Triangle Fraternity, Sports Car Club of America Give your computer some brain candy! www.distributed.net Team #1828 Windows: "Where do you want to go today?" Linux: "Where do you want to go tomorrow?" FreeBSD: "Are you guys coming, or what?"
В списке pgsql-hackers по дате отправления: