"Pavel Stehule" <[EMAIL PROTECTED]> 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/
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
