Skip site navigation (1) Skip section navigation (2)

Re: AW: relation ### modified while in use

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: AW: relation ### modified while in use
Date: 2000-10-23 09:35:17
Message-ID: 39F40655.6913181B@tpf.co.jp (view raw or flat)
Thread:
Lists: pgsql-hackers

Zeugswetter Andreas SB wrote:

> > 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 ?
As for locks,weak locks doesn't pass intensive locks.  Dba seems to be able
to alter a table at any time.

Regards.
Hiroshi Inoue


In response to

pgsql-hackers by date

Next:From: Jan WieckDate: 2000-10-23 09:48:35
Subject: Re: [HACKERS] RE: Announcing PgSQL - a Python DB-API 2.0 compliant interface to PostgreSQLL
Previous:From: Larry RosenmanDate: 2000-10-23 09:34:42
Subject: Re: testing my connection to list.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group