On Thu, Jan 6, 2011 at 5:22 PM, Stephen Frost <sfr...@snowman.net> wrote: > If it's "performance" vs. "correctness", you can guess what I'm going to > vote for, however, in this case, I can't see how either of the other > options would perform better than a discard-like approach. If people > are already using 'discard all;' then they're already throwing away > their plans for prepared queries, it strikes me as unlikely that they'd > have an issue with also getting rid of stored procedure plans. If they > do, they could certainly use the individual 'discard' statements > instead (presuming we implement this with a new discard argument).
If DISCARD ALL doesn't flush this stuff, I'd consider that an outright bug. Does it? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
