| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: MOVE LAST: why? |
| Date: | 2003-01-08 22:42:26 |
| Message-ID: | 22435.1042065746@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> writes:
> I'm suspicios if we should implement scrollable cursors
> with the combination of the current MOVE and FETCH implemen-
> tation. For example the backwards FETCH operation for group
> nodes isn't implemented properly yet(maybe).
Yeah, backwards scan is not implemented for quite a large number of plan
node types :-(. I am not sure that it is practical to fix them all.
I have been toying with the notion of making cursors on complex plans
safe for FETCH BACKWARD by sticking a MATERIAL node atop the plan, if
the top plan node isn't one that can handle backwards scan.
The trouble with this of course is that one of the main things people
like to use cursors for is huge result sets, and materializing those is
the last thing you want to do :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2003-01-08 22:52:32 | Re: Bug in pg_get_constraintdef (for deferrable constraints) |
| Previous Message | Peter Eisentraut | 2003-01-08 22:22:40 | Re: UTF-8 encoding question regarding PhpPgAdmin development |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-01-08 23:05:11 | Re: MOVE LAST: why? |
| Previous Message | Bruce Momjian | 2003-01-08 22:05:43 | Re: Shouldn't .pgpass work with anything which uses libpq? |