Re: adding wait_start column to pg_locks

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: adding wait_start column to pg_locks
Дата
Msg-id CA+TgmoYowQhMhT74AsxDib6e3LFPGvXVxVOUdP0-hMNY9c1wgw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: adding wait_start column to pg_locks  (Ian Lawrence Barwick <barwick@gmail.com>)
Ответы Re: adding wait_start column to pg_locks  (Ian Lawrence Barwick <barwick@gmail.com>)
Список pgsql-hackers
On Wed, Jan 13, 2021 at 10:40 PM Ian Lawrence Barwick <barwick@gmail.com> wrote:
> It looks like the logical place to store the value is in the PROCLOCK
> structure; ...

That seems surprising, because there's one PROCLOCK for every
combination of a process and a lock. But, a process can't be waiting
for more than one lock at the same time, because once it starts
waiting to acquire the first one, it can't do anything else, and thus
can't begin waiting for a second one. So I would have thought that
this would be recorded in the PROC.

But I haven't looked at the patch so maybe I'm dumb.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: vacuum_cost_page_miss default value and modern hardware
Следующее
От: Zhihong Yu
Дата:
Сообщение: Re: Transactions involving multiple postgres foreign servers, take 2