Re: pg_upgrade test for binary compatibility of core data types - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: pg_upgrade test for binary compatibility of core data types
Date
Msg-id 20201227190729.GB26311@telsasoft.com
Whole thread Raw
In response to Re: pg_upgrade test for binary compatibility of core data types  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: pg_upgrade test for binary compatibility of core data types
List pgsql-hackers
On Wed, Dec 16, 2020 at 11:22:23AM -0600, Justin Pryzby wrote:
> On Sun, Dec 06, 2020 at 12:02:48PM -0600, Justin Pryzby wrote:
> > I meant to notice if the binary format is accidentally changed again, which was
> > what happened here:
> > 7c15cef86 Base information_schema.sql_identifier domain on name, not varchar.
> > 
> > I added a table to the regression tests so it's processed by pg_upgrade tests,
> > run like:
> > 
> > | time make -C src/bin/pg_upgrade check oldsrc=`pwd`/11 oldbindir=`pwd`/11/tmp_install/usr/local/pgsql/bin
> 
> Per cfbot, this avoids testing ::xml (support for which may not be enabled)
> And also now tests oid types.
> 
> I think the per-version hacks should be grouped by logical change, rather than
> by version.  Which I've started doing here.

rebased on 6df7a9698bb036610c1e8c6d375e1be38cb26d5f

-- 
Justin

Attachment

pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: range_agg
Next
From: Alexander Korotkov
Date:
Subject: Re: range_agg