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

From Tom Lane
Subject Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Date
Msg-id 27738.972615915@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)  (Hiroshi Inoue <Inoue@tpf.co.jp>)
List pgsql-committers
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?

            regards, tom lane

pgsql-committers by date:

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