RE: AW: Issue NOTICE for attempt to raise lock level?

Поиск
Список
Период
Сортировка
От Mikheev, Vadim
Тема RE: AW: Issue NOTICE for attempt to raise lock level?
Дата
Msg-id 8F4C99C66D04D4118F580090272A7A234D314D@sectorbase1.sectorbase.com
обсуждение исходный текст
Ответ на AW: Issue NOTICE for attempt to raise lock level?  (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>)
Ответы Re: AW: Issue NOTICE for attempt to raise lock level?  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
> Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Zeugswetter Andreas SB
Дата:
Сообщение: AW: AW: AW: Issue NOTICE for attempt to raise lock leve l?
Следующее
От: Zeugswetter Andreas SB
Дата:
Сообщение: AW: AW: Issue NOTICE for attempt to raise lock level?