| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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: Cursor with hold emits the same row more than once across commits in 8.3.7 |
| Date: | 2009-06-09 17:54:16 |
| Message-ID: | 1244570056.21727.66.camel@monkey-cat.sm.truviso.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Tue, 2009-06-09 at 10:51 -0700, Jeff Davis wrote:
> 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.
>
Correction: I didn't actually mean _shared_ memory there. It's just
backend-local memory.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-06-09 18:00:41 | Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7 |
| Previous Message | Jeff Davis | 2009-06-09 17:51:25 | Re: Cursor with hold emits the same row more than once across commits in 8.3.7 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-06-09 17:57:49 | Re: Multicolumn index corruption on 8.4 beta 2 |
| Previous Message | Tom Lane | 2009-06-09 17:54:03 | Re: page is uninitialized --- fixing |