AW: Issue NOTICE for attempt to raise lock level?

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: AW: Issue NOTICE for attempt to raise lock level?
Date: 2000-11-08 09:42:24
Message-ID: 11C1E6749A55D411A9670001FA6879633680F8@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> relcache. Not good. Forcing the schema update to be held off in the
> first place seems the right answer.

Agreed, the only question is, how long. My idea would be until statement end,
which is also how Informix does it btw. (If you wanted a prominent example)

Of course a "statement" spans open cursor and all subsequent fetches.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas SB 2000-11-08 09:49:14 AW: AW: AW: Issue NOTICE for attempt to raise lock leve l?
Previous Message Zeugswetter Andreas SB 2000-11-08 09:03:13 AW: AW: AW: Issue NOTICE for attempt to raise lock leve l?