Re: Question about row visibility after locks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Question about row visibility after locks
Date: 2002-11-09 15:43:27
Message-ID: 3249.1036856607@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-11-09 16:17:58 Re: Problem with 7.3 on Irix with dates before 1970
Previous Message Magnus Naeslund(f) 2002-11-09 07:48:51 7.3b5 Supported platforms alpha linux update