On Sat, 9 Nov 2002, Tom Lane wrote: > Stephan Szabo <[EMAIL PROTECTED]> 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. ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
