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

From Stephan Szabo
Subject Re: Question about row visibility after locks
Date
Msg-id 20021109110211.G29283-100000@megazone23.bigpanda.com
Whole thread Raw
In response to Re: Question about row visibility after locks  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 9 Nov 2002, Tom Lane wrote:

> 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.

Okay, that's what I figured, but wanted to check before doing something
like that.



pgsql-hackers by date:

Previous
From: snpe
Date:
Subject: PostgreSQL JDBC and sub-select
Next
From: Stephan Szabo
Date:
Subject: Re: [GENERAL] PostgreSQL JDBC and sub-select