| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | 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] Re: Cursor with hold emits the same row more than once across commits in 8.3.7 |
| Date: | 2009-06-09 18:33:18 |
| Message-ID: | 25190.1244572398@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Jeff Davis <pgsql(at)j-davis(dot)com> writes:
> On Tue, 2009-06-09 at 10:51 -0700, Jeff Davis wrote:
>> 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.
> Correction: I didn't actually mean _shared_ memory there. It's just
> backend-local memory.
Well, wherever it's stored, it's a demonstrable fact that we're not
getting the same rows after ExecutorRewind(); and that we do get the
same rows out if we disable synchronize_seqscans in Mark's test case.
I haven't got round to identifying exactly what to change if we decide
to go for a narrow fix instead of storing the query results at a higher
level.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-06-09 22:01:29 | Re: [HACKERS] BUG #4822: xmlattributes encodes '&' twice |
| Previous Message | Jaime Casanova | 2009-06-09 18:15:56 | Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-09 18:44:15 | Re: Not quite a security hole in internal_in |
| Previous Message | Tom Lane | 2009-06-09 18:29:35 | Re: Not quite a security hole in internal_in |