Re: Transaction isolation and constraints

Поиск
Список
Период
Сортировка
От cliff@krumvieda.com
Тема Re: Transaction isolation and constraints
Дата
Msg-id 200712052035.lB5KZTQB024956@phumos.tgtaft.emc.com
обсуждение исходный текст
Ответ на Re: Transaction isolation and constraints  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Transaction isolation and constraints  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-general
Hi, Tom:

>Whichever one manages to get to the index page first will go through.
>The second one will block waiting to see if the first one commits,
>and will error out if so --- or proceed, if it aborts.

I see, this makes sense.  What if the two transactions insert rows
that don't violate the constraint: will they be able to proceed in
parallel?  Or will one wait for the other, because they both need to
update the shared index?  I.e., does the mechanism work by waiting for
one index update to commit before permitting the next?

                   --Cliff

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

Предыдущее
От: Paul Boddie
Дата:
Сообщение: Re: Deadlock when updating table partitions (and presumed solution)
Следующее
От: "Andrus"
Дата:
Сообщение: Re: Avoid huge perfomance loss on string concatenation