Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) - Mailing list pgsql-committers

From Philip Warner
Subject Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Date
Msg-id 3.0.5.32.20001027204352.00a06540@mail.rhyme.com.au
Whole thread Raw
In response to Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
At 20:17 26/10/00 -0400, Tom Lane wrote:
>
>Possibly the optimizer should always assume that cursors ought to
>be optimized for fast start, LIMIT or no LIMIT --- does that seem
>like a good idea to you?
>

No to me; I'd vote for an 'OPTIMIZE FOR FAST START' phrase ahead of always
doing a fast start. It also seems natural that a LIMIT clause should (a)
limit the results in all cases and (b) be used by the optimiser in such a
way that it *considers* a fast start approach more carefully.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 0500 83 82 82         |                 ___________ |
Http://www.rhyme.com.au          |                /           \|
                                 |    --________--
PGP key available upon request,  |  /
and from pgp5.ai.mit.edu:11371   |/

pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Next
From: Philip Warner
Date:
Subject: Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)