Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Date: 2000-10-27 10:43:52
Message-ID: 3.0.5.32.20001027204352.00a06540@mail.rhyme.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

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 |/

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Philip Warner 2000-10-27 10:50:17 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Previous Message Tom Lane 2000-10-27 05:20:32 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2000-10-27 10:50:17 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Previous Message Emils Klotins 2000-10-27 09:00:27 Re: renaming columns... danger?