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

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>
Cc: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: AW: AW: AW: BLERe: AW: AW: relation ### modified while in use
Date: 2000-10-24 10:15:52
Message-ID: 11C1E6749A55D411A9670001FA6879633680CC@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > Also the result would be, that the first readonly statements are allowed to
> > see schema changes, but selects after the first DML would not :-(
>
> Does it mean that even read-only statements aren't allowed
> to release locks after other DMLs ?

That is, what Tom is suggesting, but not after first DML but earlier
after transaction start. I would like to avoid this. I want read only statements
to release locks upon completion regardless of transaction state
(except in serializable isolation).

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Vince Vielhaber 2000-10-24 10:18:53 Re: Mailing list archives available?
Previous Message Hiroshi Inoue 2000-10-24 10:05:51 Re: AW: AW: BLERe: AW: AW: relation ### modified while in use