From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, pgbf(at)twiska(dot)com |
Subject: | Re: XversionUpgrade tests broken by postfix operator removal |
Date: | 2020-09-19 16:21:03 |
Message-ID: | 690698.1600532463@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com> writes:
> Here's how cross version upgrade testing works. It uses a cached version of the binaries and data directory. The cache is only refreshed if there's a buildfarm run on that branch. If not, the cached version will just sit there till kingdom come. So all this should normally need for the non-live branches is a one-off adjustment in the cached version of the regression database along the lines I have indicated. My cached versions of 9.2 and 9.3 are two years old.
Hmm, okay, so patching this on gitmaster wouldn't help anyway.
> But another alternative would be to have the buildfarm module run (on
> versions older than 9.5):
> drop operator @#@ (NONE, bigint);
> CREATE OPERATOR @#@ (
> PROCEDURE = factorial,
> RIGHTARG = bigint
> );
> On reflection I think that's probably the simplest solution. It will avoid any surprises if the cached version is rebuilt, and at the same time preserve testing the prefix operator.
Works for me.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-09-19 17:20:34 | Re: Feature proposal for psql |
Previous Message | Andrew Dunstan | 2020-09-19 16:18:58 | Re: XversionUpgrade tests broken by postfix operator removal |