Re: Cursor with hold emits the same row more than once across commits in 8.3.7 - Mailing list pgsql-bugs

From Jeff Davis
Subject Re: Cursor with hold emits the same row more than once across commits in 8.3.7
Date
Msg-id 1244569885.21727.64.camel@monkey-cat.sm.truviso.com
Whole thread Raw
In response to Re: Cursor with hold emits the same row more than once across commits in 8.3.7  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Cursor with hold emits the same row more than once across commits in 8.3.7  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-bugs
On Tue, 2009-06-09 at 12:07 -0400, Tom Lane wrote:
> We could probably fix this specific issue by refactoring things in such
> a way that the seqscan start point is frozen on the first read and
> re-used after rewinds.

I don't know what you mean by "frozen" exactly, but the start point of a
synchronized scan is stored in shared memory; otherwise, it wouldn't
know where to stop.

Regards,Jeff Davis



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7
Next
From: Jeff Davis
Date:
Subject: Re: Cursor with hold emits the same row more than once across commits in 8.3.7