Re: scrollable cursor support without MOVE statement - Mailing list pgsql-patches

From Simon Riggs
Subject Re: scrollable cursor support without MOVE statement
Date
Msg-id 1176757274.3635.364.camel@silverbirch.site
Whole thread Raw
In response to scrollable cursor support without MOVE statement  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
Responses Re: scrollable cursor support without MOVE statement  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: scrollable cursor support without MOVE statement  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
List pgsql-patches
On Wed, 2007-03-28 at 17:42 +0200, Pavel Stehule wrote:
> >
> >This is the most recent email I have on this.  Was the scrollable patch
> >applied?  If not, would you resubmit?
> >
>
> I resubmit scrollable cursor patch

I notice your patch has been accepted, though admit I hadn't noticed it
previously.

Can I ask a question relating to the patch?
How is the scrollability determined?

Scrollable cursors and sorts don't mix very well in terms of
performance, as you may know. Previously, since NOSCROLL was the only
option, this wasn't a problem. Now that we have scrollable cursors, it
is an issue, since according to the doc change the scrollability default
is neither scroll nor noscroll.

I'm concerned that many PL/pgSQL routines will now run slower because
they may now be considered scrollable when they previously were not. How
is the scrollability determined? Do we look at the kids of FETCH being
used to determine whether we need scrolling? (which would be great) Or
will we have to manually change all existing PL/pgSQL code so that it is
definitely NOSCROLL? (which would be unacceptable). Or?

--
  Simon Riggs
  EnterpriseDB   http://www.enterprisedb.com



pgsql-patches by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: patch to suppress psql timing output in quiet mode
Next
From: Tom Lane
Date:
Subject: Re: scrollable cursor support without MOVE statement