READ UNCOMMITTED in postgres - Mailing list pgsql-general

From Matthew Phillips
Subject READ UNCOMMITTED in postgres
Date
Msg-id CAFWy7AZpq1y8scTo6KeO+OLwwWt+OnC1=5iHCDSQJ_5iZd4EFw@mail.gmail.com
Whole thread Raw
Responses Re: READ UNCOMMITTED in postgres
Re: READ UNCOMMITTED in postgres
Re: READ UNCOMMITTED in postgres
List 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 by date:

Previous
From: Erik Jones
Date:
Subject: AccessExclusiveLock with pg_locks.locktype of tuple
Next
From: Stephen Frost
Date:
Subject: Re: READ UNCOMMITTED in postgres