Robert Haas <robertmh...@gmail.com> writes:
> This seems like the only option that will produce correct answers, so
> it gets my vote. How much is the performance penalty for
> materializing the tuplestore? I'm inclined to think that whatever it
> is, you just have to pay it if you ask for a WITH HOLD cursor.
I don't mind paying it for a WITH HOLD cursor, since by definition
you're asking for a more expensive behavior there. The thing that is
bothering me more is whether we want to pay a price for a *non* WITH
HOLD cursor. You can get instability for seqscan or volatile functions
if you just try MOVE BACKWARD ALL and re-read.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
