Re: pg_upgrade test for binary compatibility of core data types

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, buschmann(at)nidsa(dot)net, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_upgrade test for binary compatibility of core data types
Date: 2020-12-27 19:07:29
Message-ID: 20201227190729.GB26311@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs 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 Content-Type Size
v3-0001-WIP-pg_upgrade-test.sh-changes-needed-to-allow-te.patch text/x-diff 5.2 KB
v3-0002-pg_upgrade-test-to-exercise-binary-compatibility.patch text/x-diff 5.8 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniele Varrazzo 2020-12-28 01:27:08 Missing compiled default for channel_binding param from PQconndefaults
Previous Message PG Bug reporting form 2020-12-27 17:18:36 BUG #16792: silent corruption of GIN index resulting in SELECTs returning non-matching rows

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2020-12-27 19:31:27 Re: range_agg
Previous Message David Fetter 2020-12-27 18:07:51 Re: range_agg