On Tue, Apr 25, 2006 at 12:48:04PM -0400, Alvaro Herrera wrote:
I'm late to this thread, but maybe we can make the process of storing
the new data in pg_class take a lock using LockObject() or something
like that to serialize the access to the pg_class row. The idea would
be that this lock
On Tue, Apr 25, 2006 at 12:25:35PM -0500, Jim C. Nasby wrote:
Is there anything in comments/docs/list archives about why catalog
access uses a bunch of 'magic' instead of treating catalog tables the
same as every other table? I realize that ultimately you have to
bootstrap somehow (kinda hard
Martijn van Oosterhout kleptog@svana.org writes:
I think the basic problem is that DDL can't really work within a
transaction. If I do an ALTER TABLE, some of these changes need to show
up to concurrent transactions (maybe creating a unique index?).
The point is that DDL can't be MVCC. If for
