READ UNCOMMITTED in postgres

Поиск
Список
Период
Сортировка
От Matthew Phillips
Тема READ UNCOMMITTED in postgres
Дата
Msg-id CAFWy7AZpq1y8scTo6KeO+OLwwWt+OnC1=5iHCDSQJ_5iZd4EFw@mail.gmail.com
обсуждение исходный текст
Ответы Re: READ UNCOMMITTED in postgres  (Stephen Frost <sfrost@snowman.net>)
Re: READ UNCOMMITTED in postgres  (Thomas Kellerer <spam_eater@gmx.net>)
Re: READ UNCOMMITTED in postgres  (Simon Riggs <simon@2ndquadrant.com>)
Список pgsql-general
Hi,
With the current READ UNCOMMITTED discussion happening on pgsql-hackers [1], It did raise a question/use-case I recently encountered and could not find a satisfactory solution for. If someone is attempting to poll for new records on a high insert volume table that has a monotonically increasing id, what is the best way to do it? As is, with a nave implementation, rows are not guaranteed to appear in monotonic order; so if you were to keep a $MAX_ID, and SELECT WHERE p_id > $MAX_ID, you would hit gaps. Is there a clean way to do this? I've seen READ UNCOMMITTED used for this with DB2.

Thanks
Matt

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

Предыдущее
От: Erik Jones
Дата:
Сообщение: AccessExclusiveLock with pg_locks.locktype of tuple
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: READ UNCOMMITTED in postgres