Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set
Дата
Msg-id CAKFQuwbjXa2FxwDhikV1uZSZaQb53_CRCPNxs7-rtDYjwT6s5g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs


On Tuesday, February 28, 2023, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"David G. Johnston" <david.g.johnston@gmail.com> writes:

> It is unclear to me whether you were instead talking about other sessions
> dropping tables as another way of saying "ACCESS EXCLUSIVE" in which case
> at what lock level should this anomaly go away, and does it?

The originally-proposed tests seemed to all involve either TRUNCATE
or DROP TABLE,

The only purpose of those was to produce a self-contained script that could be run repeatedly.  The commands were outside the transaction flow demonstrating the issue.

David J.
 

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

Предыдущее
От: Felipe Die
Дата:
Сообщение: Gpg error with Postgresql aarch64 repo - PG14
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #17812: LOCK TABLE IN ACCESS EXCLUSIVE MODE with a view returns an empty tuple set