From: | "Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | neilc(at)samurai(dot)com, pgsql-patches(at)postgresql(dot)org, jonah(dot)harris(at)gmail(dot)com |
Subject: | Re: scrollable cursor sup. for SPI |
Date: | 2007-01-16 06:52:37 |
Message-ID: | BAY20-F89195A851D0C3CB2065F5F9B40@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
>
>"Pavel Stehule" <pavel(dot)stehule(at)hotmail(dot)com> writes:
> > if I comprehended it well CURSOR_OPT_SCROLL is set only when SCROLL is
>cheap
> > (not when is possible). It's true?
>
>Nope. If you want a scrollable plan you need to make sure you tell the
>planner about it. SPI_cursor_open is not in charge, it's merely looking
>at what the planner did.
aha. Then modification of open function hasn't sence. But it needs enhance
SPI_prepare. I don't know when cursors are not scrollable implicitly. it
it's important. If not, then I need for scrollable cursors in plpgsql only
fetch and move scroll funcs.
Pavel Stehule
_________________________________________________________________
Citite se osamele? Poznejte nekoho vyjmecneho diky Match.com.
http://www.msn.cz/
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2007-01-16 07:37:00 | Re: pg_dumpall default database |
Previous Message | Tom Lane | 2007-01-16 04:57:27 | Re: pg_dumpall default database |