I have a procedure that queries a table. This should be fast because of an
index, but some index bloat has caused the index to become expensive, and so
the procedure has cached a plan that uses a full table scan. I've since fixed
the index bloat, but the procedure still seems to be doing full table scans. Is
there a non-disruptive way to invalidate the cached plan for that procedure
globally?
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
