On Tue, Apr 28, 2015 at 12:43 PM, Robert Haas <robertmh...@gmail.com> wrote: > I hate to use the term "bug" for what somebody's probably going to > tell me is acceptable behavior, but that seems like a bug. I guess > the root of the problem is that PL/plgsql's cache invalidation logic > only considers the pg_proc row's TID and xmin when deciding whether to > recompile. For base types that's probably OK, but for composite > types, not so much.
It was a missed case in the invalidation logic. plpgsql was deliberately modified to invalidate plans upon schema changes -- this is a way to outsmart that system. definitely a bug IMNSHO. merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
