SKIP LOCKED DATA (work in progress) - Mailing list pgsql-hackers

From Thomas Munro
Subject SKIP LOCKED DATA (work in progress)
Date
Msg-id CADLWmXUvd5Z+cFczi6Zj1WcTrXzipgP-wj0pZOWSaRUy=F0omQ@mail.gmail.com
Whole thread Raw
Responses Re: SKIP LOCKED DATA (work in progress)
Re: SKIP LOCKED DATA (work in progress)
List pgsql-hackers
Hi

A couple of years ago I posted an outline of a plan [1] and an
initial patch [2] for implementing SKIP LOCKED DATA.  I have
recently come back to this idea, rebased the patch and added a
simple isolation test -- please see attached.

However, heap_lock_tuple is clearly not for the faint hearted,
and I freely admit that I don't understand half of the things
going on in there yet.  My general approach has been to follow
the example set by NOWAIT, generalising that flag into a 3-way
policy...  but of course NOWAIT doesn't have to worry about
cleaning anything up, because it uses ereport, hence my TODOs.

As always, I would be grateful for any feedback.

Thanks!

Thomas Munro


Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: gettimeofday is at the end of its usefulness?
Next
From: Craig Ringer
Date:
Subject: Re: SKIP LOCKED DATA (work in progress)