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 04:24:42 |
Message-ID: | 28019.972620682@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:
> begin;
> declare myc cursor for select * from t1 limit all;
> fetch 20 in myc; (the first page)
> ...(interaction)
> fetch 20 in myc; (the next page)
> ..(interaction)
> fetch backward 20 in myc; (the previous page)
> ...
> What I expect here is to get rows of each page in
> an average response time not the total throughput
> of db operation.
Yes, but why should the presence of "limit all" affect that?
It's not apparent to me why the optimizer should treat this
case differently from plain
declare myc cursor for select * from t1;
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-10-27 04:31:20 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
Previous Message | Hiroshi Inoue | 2000-10-27 03:59:02 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2000-10-27 04:31:20 | Re: pgsql/src/backend/nodes (copyfuncs.c outfuncs.c print.c) |
Previous Message | Lamar Owen | 2000-10-27 04:07:16 | PostgreSQL article in Linux Journal Nov 2000 |