Lock conflict

Поиск
Список
Период
Сортировка
От 席冲(宜穆)
Тема Lock conflict
Дата
Msg-id 2db0313d-7097-4b95-b4a3-02dea4d65c5a.xichong.xc@alibaba-inc.com
обсуждение исходный текст
Ответы Re: Lock conflict  (David Rowley <dgrowleyml@gmail.com>)
Список pgsql-hackers
Дерево обсуждения

Hello all,


This PostgreSQL version is 11.9.

In LockAcquireExtended(), why if lock requested conflicts with locks requested by waiters, must join
wait queue. Why does the lock still check for conflict with the lock requested,
rather than check for directly with conflict with the already-held lock?

I think lock requested only check for conflict with already-held lock, if there is no conflict, the lock should be granted.

Best regards



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

Предыдущее
От: "wangw.fnst@fujitsu.com"
Дата:
Сообщение: RE: Data is copied twice when specifying both child and parent table in publication
Следующее
От: David Rowley
Дата:
Сообщение: Re: Lock conflict