| 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 00:17:23 |
| Message-ID: | 23437.972605843@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:
> It seems to me that LIMIT in declare cursor statement is only
> for optimizer's hint.
I think that would just confuse people. 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.
Possibly the optimizer should always assume that cursors ought to
be optimized for fast start, LIMIT or no LIMIT --- does that seem
like a good idea to you?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hiroshi Inoue | 2000-10-27 00:47:32 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
| Previous Message | Hiroshi Inoue | 2000-10-27 00:09:33 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-10-27 00:17:27 | Re: Summary: what to do about INET/CIDR |
| Previous Message | Hiroshi Inoue | 2000-10-27 00:09:33 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |