| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <peter(at)2ndquadrant(dot)com> |
| Subject: | Re: assertion failure w/extended query protocol |
| Date: | 2012-10-20 03:37:07 |
| Message-ID: | 17767.1350704227@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> On Saturday, October 20, 2012 12:05:15 AM Tom Lane wrote:
>> (such as the current query showing up in pg_cursors --- maybe we should
>> prevent that?)
> I don't really see an argument for preventing that.
Well, the reason it seems peculiar to me is that the current query is in
no way a cursor --- it's just a SELECT in the cases that showed
regression test differences. I didn't go looking in the code yet, but
I suspect the pg_cursors view is displaying all Portals. Arguably, it
should only display those that were created by actual cursor commands.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Lee | 2012-10-20 05:57:52 | Foreign key constraint on sub-column of composite-type column |
| Previous Message | Andrew Dunstan | 2012-10-20 02:19:11 | Re: assertion failure w/extended query protocol |