| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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-09 17:38:51 |
| Message-ID: | 20090609173851.GG5938@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Robert Haas escribió:
> I suppose in theory you could try to figure out whether
> materialization is really necessary (let's see... no seqscans here and
> no volatile functions... ok, so we can cheat...) but that seems
> likely to lead to future bugs as the rules for which things are safe
> change.
Another thing we could do is disable syncscan if we see a WITH HOLD
cursor, but I guess it's not future-proof either.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-09 17:47:14 | Re: [HACKERS] Cursor with hold emits the same row more than once across commits in 8.3.7 |
| Previous Message | Robert Haas | 2009-06-09 17:37:07 | 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 17:44:16 | Re: Not quite a security hole in internal_in |
| Previous Message | Alvaro Herrera | 2009-06-09 17:37:35 | Re: Multicolumn index corruption on 8.4 beta 2 |