Re: [GENERAL] Using xmin and xmax for optimistic locking

Поиск
Список
Период
Сортировка
Искать
От
Tom Lane
Тема
Re: [GENERAL] Using xmin and xmax for optimistic locking
Дата
Msg-id
11074.1487625771@sss.pgh.pa.us
Ответ на
Список
Дерево обсуждения
[GENERAL] Using xmin and xmax for optimistic locking Rakesh Kumar <rakeshkumar464@outlook.com>
Re: [GENERAL] Using xmin and xmax for optimistic locking Karsten Hilbert <Karsten.Hilbert@gmx.net>
Re: [GENERAL] Using xmin and xmax for optimistic locking Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Using xmin and xmax for optimistic locking Karsten Hilbert <Karsten.Hilbert@gmx.net>
Re: [GENERAL] Using xmin and xmax for optimistic locking Tom Lane <tgl@sss.pgh.pa.us>
Re: [GENERAL] Using xmin and xmax for optimistic locking Karsten Hilbert <Karsten.Hilbert@gmx.net>
Karsten Hilbert  writes:
> Also a consideration: table.*::text may become quite unwieldy
> if there's one or more BYTEA columns in the table.

One other thought here --- if you do want to go with the "no other
updates" semantics, it still seems like it should be sufficient to
compare xmins.  Comparing the xmax values would add nothing to that,
except that it would reject if another update had been attempted and
then failed, which seems undesirable.

			regards, tom lane

В списке pgsql-general по дате отправления
От: Karsten Hilbert
Дата:
От: Karsten Hilbert
Дата:
FAQ