Horton
Menu

Re: assertion failure w/extended query protocol

Tom Lane <tgl@sss.pgh.pa.us>

View thread
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, pgsql-hackers@postgresql.org, Peter Geoghegan <peter@2ndquadrant.com>
Date: 2012-10-20T03:37:07Z
Lists: pgsql-hackers 
Andres Freund <andres@2ndquadrant.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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Restructure SELECT INTO's parsetree representation into CreateTableAsStmt.