Re: Question about row visibility after locks - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Question about row visibility after locks
Date
Msg-id 3249.1036856607@sss.pgh.pa.us
Whole thread Raw
In response to Question about row visibility after locks  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
Responses Re: Question about row visibility after locks  (Stephan Szabo <sszabo@megazone23.bigpanda.com>)
List pgsql-hackers
Stephan Szabo <sszabo@megazone23.bigpanda.com> writes:
> Basically, if I've got a select that's running using
> HeapTupleSatisfiesDirty so that I can see uncommitted rows
> and I block in the middle for another transaction (waiting
> to see if it commits the row I'm looking at) and that
> transaction inserts another row that meets my search criteria
> am I guaranteed to see that second row in all cases?

No; it might get inserted into a page you've already scanned over.
You'd have to restart your scan if you wanted that.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Magnus Naeslund(f)"
Date:
Subject: 7.3b5 Supported platforms alpha linux update
Next
From: Tom Lane
Date:
Subject: Re: Problem with 7.3 on Irix with dates before 1970