| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Mikheev, Vadim'" <vmikheev(at)SECTORBASE(dot)COM>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: AW: Issue NOTICE for attempt to raise lock level? |
| Date: | 2000-11-07 18:11:38 |
| Message-ID: | 11C1E6749A55D411A9670001FA6879633680F5@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > In the second place, we already grab locks that we do not release till
> > end of xact for all user-level queries. The problem is that we grab
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Even for select?
No. Tom plans to change that, and I still think this is a bad idea.
> > them too late, ie, in the executor. I'm just planning to move up the
> > grab till first use.
This would be good.
> BTW, what about indices?
Same here, would need to be released after each readonly statement.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2000-11-07 18:22:19 | Could turn on -O2 in AIX |
| Previous Message | Zeugswetter Andreas SB | 2000-11-07 18:06:21 | AW: AW: AW: Issue NOTICE for attempt to raise lock leve l? |