Re: cache invalidation for PL/pgsql functions - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: cache invalidation for PL/pgsql functions
Date
Msg-id CAHyXU0wYKStLcAWy6CLEqwnoKZNtH3mPm-gGHdZGn41m0-tTWQ@mail.gmail.com
Whole thread Raw
In response to cache invalidation for PL/pgsql functions  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Tue, Apr 28, 2015 at 12:43 PM, Robert Haas <robertmhaas@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



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: INSERT ... ON CONFLICT syntax issues
Next
From: Tom Lane
Date:
Subject: Re: COPY and file_fdw with fixed column widths