Robert Haas escribió: > I suppose in theory you could try to figure out whether > materialization is really necessary (let's see... no seqscans here and > no volatile functions... ok, so we can cheat...) but that seems > likely to lead to future bugs as the rules for which things are safe > change.
Another thing we could do is disable syncscan if we see a WITH HOLD cursor, but I guess it's not future-proof either. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
