| 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 00:47:32 |
| Message-ID: | 39F8D0A4.A9A22EE1@tpf.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Tom Lane wrote:
> Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> > It seems to me that LIMIT in declare cursor statement is only
> > for optimizer's hint.
>
> I think that would just confuse people.
It could be. However what does LIMIT mean ?
Rows per FETCH ? Probably no.
FETCH forward,backward,forward,backward,.... and suddenly EOF ?
> If we want to have a hint
> that says "optimize for fast start", it ought to be done in another
> way than saying that SELECT ... LIMIT means different things in
> different contexts.
>
Yes I want to give optimizer a hint "return first rows fast".
When Jan implemented LIMIT first,there was an option
"LIMIT ALL" and it was exactly designed for the purpose.
Regards.
Hiroshi Inoue
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-27 00:59:16 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
| Previous Message | Tom Lane | 2000-10-27 00:17:23 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-10-27 00:49:22 | Re: Re: [GENERAL] A rare error |
| Previous Message | Tom Lane | 2000-10-27 00:29:52 | Re: 7.0 vs. 7.1 (was: latest version?) |