| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-06-10 18:00:46 | Re: BUG #4849: intermittent future timestamps |
| Previous Message | David Leppik | 2009-06-10 17:10:49 | Re: BUG #4849: intermittent future timestamps |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2009-06-10 17:40:16 | Re: Plan time Improvement - 64bit bitmapset |
| Previous Message | Ana Carolina Brito de Almeida | 2009-06-10 17:06:32 | PlannerInfo Structure |