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.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
