Jan Wieck [EMAIL PROTECTED] writes:
IIRC the patch only provides the syntax for CURSOR to
PL/pgSQL. Not real cursor support on the SPI level. So it's
still the same as before, the backend will try to suck up the
entire resultset into the SPI tuple table (that's
Jan Wieck [EMAIL PROTECTED] writes:
I don't object if we can be sure that it's implementing the
syntax a final version with *real* cursor support will have.
Can we?
I don't know, and I don't know what the decision criteria are.
I intentionally implemented the Oracle cursor
Ian Lance Taylor wrote:
Jan Wieck [EMAIL PROTECTED] writes:
I don't object if we can be sure that it's implementing the
syntax a final version with *real* cursor support will have.
Can we?
I don't know, and I don't know what the decision criteria are.
I intentionally
Now that 7.1 is safely in the can, is it time to consider
this patch? It provides cursor support in PL.
http://www.airs.com/ian/postgresql-cursor.patch
Nathan Myers
[EMAIL PROTECTED]
---(end of broadcast)---
TIP 2: you can get off all lists at
[EMAIL PROTECTED] (Nathan Myers) writes:
Now that 7.1 is safely in the can, is it time to consider
this patch?
Not till we've forked the tree for 7.2, which is probably a week or so
away...
regards, tom lane
---(end of
Tom Lane wrote:
[EMAIL PROTECTED] (Nathan Myers) writes:
Now that 7.1 is safely in the can, is it time to consider
this patch?
Not till we've forked the tree for 7.2, which is probably a week or so
away...
IIRC the patch only provides the syntax for CURSOR to
PL/pgSQL.