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

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Date: 2000-10-27 03:04:33
Message-ID: 39F8F0C1.9D452337@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Tom Lane wrote:

> Now that I look at it, the optimizer *already* prefers fast-start plans
> for cursors. Is LIMIT ALL really necessary as an additional hint,
> and if so how should it interact with the bias for cursors?
>

If LIMIT doesn't restrict the total count of rows which cursors
could return,there's no problem. Otherwise LIMIT ALL would be
needed.

Hiroshi Inoue

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2000-10-27 03:05:15 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Previous Message Tom Lane 2000-10-27 02:54:28 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2000-10-27 03:05:15 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Previous Message Tom Lane 2000-10-27 02:54:28 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)