| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Boszormenyi Zoltan <zb(at)cybertec(dot)at> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Meskes <meskes(at)postgresql(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Hans-Jürgen Schönig <hs(at)cybertec(dot)at> |
| Subject: | Re: Modify the DECLARE CURSOR command tag depending on the scrollable flag |
| Date: | 2013-11-27 21:22:53 |
| Message-ID: | 529662AD.5020004@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/27/13, 3:47 PM, Tom Lane wrote:
> Given these considerations, I think it'd be better to allow explicit
> application control over whether read-ahead happens for a particular
> query. And I have no problem whatsoever with requiring that the cursor
> be explicitly marked SCROLL or NO SCROLL before read-ahead will occur.
Well, technically, unspecified means NO SCROLL according to the SQL
standard. A lot of applications in ECPG are ported from other systems,
which might make that assumption. It wouldn't be very nice to have to
change all that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-11-27 21:33:20 | Re: 9.2.1 & index-only scans : abnormal heap fetches after VACUUM FULL |
| Previous Message | Peter Eisentraut | 2013-11-27 21:21:39 | Re: Modify the DECLARE CURSOR command tag depending on the scrollable flag |