Re: assertion failure w/extended query protocol - Mailing list pgsql-hackers

From Tom Lane
Subject Re: assertion failure w/extended query protocol
Date
Msg-id 17767.1350704227@sss.pgh.pa.us
Whole thread Raw
In response to Re: assertion failure w/extended query protocol  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: assertion failure w/extended query protocol  (Rushabh Lathia <rushabh.lathia@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: assertion failure w/extended query protocol
Next
From: Amit kapila
Date:
Subject: Re: [WIP PATCH] for Performance Improvement in Buffer Management