Re: Cursor not getting all rows - Mailing list pgsql-general

From Tom Lane
Subject Re: Cursor not getting all rows
Date
Msg-id 810.1116352586@sss.pgh.pa.us
Whole thread Raw
In response to Cursor not getting all rows  (Joseph Shraibman <jks@selectacast.net>)
List pgsql-general
Joseph Shraibman <jks@selectacast.net> writes:
> I do this:

> BEGIN;
> SELECT count(*) FROM u, d WHERE u.id = d.id AND ... ;
> DECLARE cname CURSOR FOR SELECT u.field, d.field FROM u, d WHERE u.id =
> d.id AND ... ;

> At the end of the fetching if the number of fetched does not equal the
> number from the SELECT count(*) I print out a warning message.  It
> happens every once in a while.  Today it happened four times.

> How is this possible?  Because they are in the same transaction the
> count and the cursor should see the exact same data, right?

Not unless you are using SERIALIZABLE mode --- otherwise the cursor will
see whatever changes were committed during execution of the first SELECT.

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: initdb: failed
Next
From: Scott Marlowe
Date:
Subject: Re: Cursor not getting all rows