From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
---|---|
To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | RE: AW: Issue NOTICE for attempt to raise lock level? |
Date: | 2000-11-07 17:54:14 |
Message-ID: | 8F4C99C66D04D4118F580090272A7A234D314D@sectorbase1.sectorbase.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
> >> I am working on eliminating the "relation NNN modified
> while in use"
> >> misfeature by instead grabbing a lock on each relation at first use
> >> in a statement, and holding that lock till end of transaction.
>
> > As anticipated, I object :-)
>
> Your objection is founded on two misunderstandings. In the
> first place, we are *always* inside a transaction when executing
> a query. It may be an implicit one-statement transaction, but it's
> still a transaction.
> 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?
> them too late, ie, in the executor. I'm just planning to move up the
> grab till first use.
BTW, what about indices?
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-11-07 17:56:46 | Re: AW: AW: Issue NOTICE for attempt to raise lock level? |
Previous Message | Hannu Krosing | 2000-11-07 17:41:02 | Re: AW: AW: Issue NOTICE for attempt to raise lock level? |