Re: Lock problem

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Lock problem
Дата
Msg-id 9342.1315441747@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Lock problem  (Eduardo Piombino <drakorg@gmail.com>)
Ответы Re: Lock problem
Список pgsql-general
Eduardo Piombino <drakorg@gmail.com> writes:
> I don't see how a new update to the same record in A, makes the difference
> to allow or deny the lock on a row on table B;

I think it's probably explained by this:

> PS: The only relation between A and B is that A has a two FKs to B, but none
> of them are even included in the updates.

IIRC there are some optimizations in the FK stuff that don't apply once
a single transaction has updated a relevant row more than once.  You
haven't given enough details (not even a PG version) to be sure about
it, but that's what I'd bet on.

            regards, tom lane

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

Предыдущее
От: Eduardo Piombino
Дата:
Сообщение: Lock problem
Следующее
От: Fujii Masao
Дата:
Сообщение: Re: master-side counterpart of pg_last_xact_replay_timestamp?