| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Scrollable cursors and Sort performance |
| Date: | 2006-02-10 16:22:44 |
| Message-ID: | 20060210162244.GQ57845@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Fri, Feb 10, 2006 at 01:32:44PM +0000, Simon Riggs wrote:
> I intend to add a short patch to pass down the cursor state during
> planning, so that when it is explicitly specified the sort node is able
> to recognise this and avoid work. Also, to add a GUC to force the
> not-explicitly-specified case to be the same as the NO SCROLL case, as
> the standard requires.
So is this only an issue if you're using a cursor, or does this affect
plain SELECT ... ORDER BY as well?
Reason I'm asking is that users should be able to explicitly be able to
turn the extra step off somehow. I'm not clear if NO SCROLL is
sufficient to do that or not.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-10 16:31:13 | Re: Backslashes in string literals |
| Previous Message | Simon Riggs | 2006-02-10 16:12:42 | Re: Scrollable cursors and Sort performance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-02-10 16:28:34 | Re: pgsql: Allow psql multi-line column values to align |
| Previous Message | Simon Riggs | 2006-02-10 16:12:42 | Re: Scrollable cursors and Sort performance |