Re: Postgresql9.6 type cache invalidation issue - different behave ofpsql and pg regress - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Postgresql9.6 type cache invalidation issue - different behave ofpsql and pg regress
Date
Msg-id CAFj8pRCfWmcXuCDuAkHAv7P9iNvvV_+-P4x2pE3UYCuO0U-QOg@mail.gmail.com
Whole thread Raw
In response to Re: Postgresql9.6 type cache invalidation issue - different behave of psql and pg regress  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers


2018-04-20 15:44 GMT+02:00 Tom Lane <tgl@sss.pgh.pa.us>:
Pavel Stehule <pavel.stehule@gmail.com> writes:
> In interactive mode, the build_row_from_class has unrefreshed metadata. But
> why this behave I see only in psql and not in my regress tests?

The short answer is that no plpgsql version before commit 4b93f5799
will have nice behavior for cases where you change a referenced composite
type between calls.  Why that's translating to the particular behavior
you're seeing isn't clear, considering you showed only one case in
detail; but I imagine it's because a parse of the plpgsql function
happens before the ALTER TABLE in one case and not the other.
Perhaps you have different settings of check_function_bodies,
for instance.

good catch - I had check_function_bodies disabled.

Thank you for reply. Now I can believe to my regress tests again :)

Regards

Nice weekend

Pavel


                        regards, tom lane

pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: [HACKERS] proposal: schema variables
Next
From: Alvaro Herrera
Date:
Subject: Re: Should we add GUCs to allow partition pruning to be disabled?