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

From Hiroshi Inoue
Subject Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Date
Msg-id 39F8F265.C27990D7@tpf.co.jp
Whole thread Raw
In response to pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)  (Tom Lane <tgl@postgresql.org>)
Responses Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
List pgsql-committers

Tom Lane wrote:

> Hiroshi Inoue <Inoue@tpf.co.jp> writes:
> > 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.
>
> But is there a reason to treat LIMIT ALL differently from no LIMIT
> clause at all?
>

For example,LIMIT ALL means LIMIT 1 for optimizer and means
no LIMIT for executor.
Comments ?

Regards, Hiroshi Inoue.



pgsql-committers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: pgsql/src/test/regress/expected (euc_jp.out)
Next
From: Hiroshi Inoue
Date:
Subject: Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)