Re: READ UNCOMMITTED in postgres

Поиск
Список
Период
Сортировка
От Stephen Frost
Тема Re: READ UNCOMMITTED in postgres
Дата
Msg-id 20191218232003.GZ3195@tamriel.snowman.net
обсуждение исходный текст
Ответ на READ UNCOMMITTED in postgres  (Matthew Phillips <mphillips34@gmail.com>)
Список pgsql-general
Greetings,

* Matthew Phillips (mphillips34@gmail.com) wrote:
> 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.

There's the LISTEN/NOTIFY system, which at a high level is a better
approach than using a polling system.

Thanks,

Stephen

Вложения

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

Предыдущее
От: Matthew Phillips
Дата:
Сообщение: READ UNCOMMITTED in postgres
Следующее
От: Tom Lane
Дата:
Сообщение: Re: AccessExclusiveLock with pg_locks.locktype of tuple