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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: 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 03:14:14
Message-ID: 27840.972616454@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> For example,LIMIT ALL means LIMIT 1 for optimizer and means
> no LIMIT for executor.
> Comments ?

I don't see the point. In the context of a regular SELECT, optimizing
that way would be wrong, because we are going to fetch all the data.
In the context of a DECLARE CURSOR, we already have a bias for fast-
start plans, so why do we need another?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-10-27 03:32:51 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Previous Message Bruce Momjian 2000-10-27 03:12:38 Re: pgsql (configure)

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 2000-10-27 03:32:51 Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c)
Previous Message Bruce Momjian 2000-10-27 03:11:34 Re: 7.0 vs. 7.1 (was: latest version?)