AW: AW: relation ### modified while in use - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: AW: relation ### modified while in use
Date
Msg-id 11C1E6749A55D411A9670001FA6879633680C2@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses Re: AW: AW: relation ### modified while in use  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> > > What I'm proposing is that once an xact has touched a
> > > table, other xacts should not be able to apply schema updates to that
> > > table until the first xact commits.
> >
> > No, this would mean too many locks, and would leave the dba with hardly a
> > chance to alter a table.
> >
> 
> Are there many applications which have many SELECT statements(without
> FOR UPDATE) in one tx ?

Why not ?

> As for locks,weak locks doesn't pass intensive locks.  Dba 
> seems to be able to alter a table at any time.

Sorry, I don't understand this sentence. Tom suggested placing a shared lock on 
any table that is accessed until end of tx. Noone can alter table until all users have
closed their txns and not accessed tables again. Remember that this would include
creating an index ...

Andreas


pgsql-hackers by date:

Previous
From: Larry Rosenman
Date:
Subject: Re: testing my connection to list.
Next
From: Hiroshi Inoue
Date:
Subject: Re: AW: relation ### modified while in use