Re: on placeholder entries in view rule action query's range table - Mailing list pgsql-hackers

From Tom Lane
Subject Re: on placeholder entries in view rule action query's range table
Date
Msg-id 869374.1673495133@sss.pgh.pa.us
Whole thread Raw
In response to Re: on placeholder entries in view rule action query's range table  (Amit Langote <amitlangote09@gmail.com>)
Responses Re: on placeholder entries in view rule action query's range table
Re: on placeholder entries in view rule action query's range table
List pgsql-hackers
Amit Langote <amitlangote09@gmail.com> writes:
>  On Thu, Jan 12, 2023 at 10:06 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I've pushed this with some cleanup --- aside from fixing
>> outfuncs/readfuncs, I did some more work on the comments, which
>> I think you were too sloppy about.

> Thanks a lot for the fixes.

It looks like we're not out of the woods on this: the buildfarm
members that run cross-version-upgrade tests are all unhappy.
Most of them are not reporting any useful details, but I suspect
that they are barfing because dumps from the old server include
table-qualified variable names in some CREATE VIEW commands while
dumps from HEAD omit the qualifications.  I don't see any
mechanism in TestUpgradeXversion.pm that could deal with that
conveniently, and in any case we'd have to roll out a client
script update to the affected animals.  I fear we may have to
revert this pending development of better TestUpgradeXversion.pm
support.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Blocking execution of SECURITY INVOKER
Next
From: Peter Geoghegan
Date:
Subject: Re: Fixing a couple of buglets in how VACUUM sets visibility map bits