Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Robert Haas <robertmhaas(at)gmail(dot)com>, Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7
Date: 2009-06-10 17:16:19
Message-ID: 8133.1244654179@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-hackers
Given that RC freeze is nearly upon us for 8.4, and that we need a
reasonably non-invasive fix for 8.3 anyway, I propose that for now
we just deal with the syncscan issue by tweaking heap_rescan so that
rs_startblock doesn't get changed.  It looks like that's about a
three-line patch.  The question of how cursors should behave with
respect to volatile functions can be documented and left for another
time.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andres FreundDate: 2009-06-10 17:40:16
Subject: Re: Plan time Improvement - 64bit bitmapset
Previous:From: Ana Carolina Brito de AlmeidaDate: 2009-06-10 17:06:32
Subject: PlannerInfo Structure

pgsql-bugs by date

Next:From: Kevin GrittnerDate: 2009-06-10 18:00:46
Subject: Re: BUG #4849: intermittent future timestamps
Previous:From: David LeppikDate: 2009-06-10 17:10:49
Subject: Re: BUG #4849: intermittent future timestamps

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group