Re: Question about row visibility after locks

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

On Sat, 9 Nov 2002, Tom Lane wrote:

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

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephan Szabo 2002-11-09 19:07:17 Re: PostgreSQL JDBC and sub-select
Previous Message snpe 2002-11-09 17:51:41 PostgreSQL JDBC and sub-select