AW: AW: LIMIT in DECLARE CURSOR: request for comments

From: Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: AW: AW: LIMIT in DECLARE CURSOR: request for comments
Date: 2000-11-03 16:32:21
Message-ID: 11C1E6749A55D411A9670001FA6879633680E4@sdexcsrv1.f000.d0188.sd.spardat.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > There is no way for the backend to know this, thus imho the app needs
> > to give a hint.
>
> Right. So what do you think about a hint that takes the form of a SET
> variable for the fetch percentage to assume for a DECLARE CURSOR?

Since we don't have other hints that are embedded directly into the SQL
that sounds perfect.

The not so offhand question for me is whether to use this percentage for
non cursor selects also. Imho both should (at least in default) behave the same.

Andreas

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-11-03 16:59:49 Re: AW: AW: LIMIT in DECLARE CURSOR: request for comments
Previous Message Thomas Lockhart 2000-11-03 16:25:23 INTERVAL representation