Re: SELECT FOR UPDATE and LIMIT 1 behave oddly

Поиск
Список
Период
Сортировка
Искать
От
andrea suisani
Тема
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly
Дата
Msg-id
4193F088.2040905@demetra.com
Ответ на
Список
Дерево обсуждения
SELECT FOR UPDATE and LIMIT 1 behave oddly Josh Berkus <josh@agliodbs.com>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Tom Lane <tgl@sss.pgh.pa.us>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Neil Conway <neilc@samurai.com>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Tom Lane <tgl@sss.pgh.pa.us>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Neil Conway <neilc@samurai.com>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Tom Lane <tgl@sss.pgh.pa.us>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Neil Conway <neilc@samurai.com>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Josh Berkus <josh@agliodbs.com>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Oliver Elphick <olly@lfix.co.uk>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Bruce Momjian <pgman@candle.pha.pa.us>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Josh Berkus <josh@agliodbs.com>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly andrea suisani <suisani@demetra.com>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Bruce Momjian <pgman@candle.pha.pa.us>
Re: SELECT FOR UPDATE and LIMIT 1 behave oddly Josh Berkus <josh@agliodbs.com>
hi!

Josh Berkus wrote:
 > Bruce,
 >

[snip]

 >
 >
 > Well, limit+for update can be useful under some circumstances, as long as you
 > understand its limitations.    We found a workaround.

i'm sorry for the curiosity.... but
could you share, if it's possible, this workaround? ;)


andrea
В списке pgsql-bugs по дате отправления
От: Ganesh and Sashi Prasad
Дата:
От: Andrea Suisani
Дата:
FAQ