pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jacob Champion <pchampion@vmware.com>
Cc: pryzby@telsasoft.com <pryzby@telsasoft.com>
Cc: peter.eisentraut@enterprisedb.com <peter.eisentraut@enterprisedb.com>
Cc: pgsql-hackers@lists.postgresql.org <pgsql-hackers@lists.postgresql.org>
Cc: buschmann@nidsa.net <buschmann@nidsa.net>
Cc: andrew@dunslane.net <andrew@dunslane.net>
Cc: noah@leadboat.com <noah@leadboat.com>
Cc: tomas.vondra@2ndquadrant.com <tomas.vondra@2ndquadrant.com>
Cc: bruce@momjian.us <bruce@momjian.us>
Cc: andres@anarazel.de <andres@anarazel.de>
Subject: Re: pg_upgrade test for binary compatibility of core data types
Date: Sat, 11 Sep 2021 14:19:04 -0400
Message-ID: <105345.1631384344@sss.pgh.pa.us> (raw)
In-Reply-To: <a31d593da98da15fc2302a16b3f3b32e491d3e49.camel@vmware.com>
References: <20201216172222.GS30237@telsasoft.com>
	<20201227190729.GB26311@telsasoft.com>
	<be693563-def1-2f5a-89c1-f4d3cb2ae716@enterprisedb.com>
	<20210112041352.GY1849@telsasoft.com>
	<20210112171559.GO4320@momjian.us>
	<20210112172753.GC1849@telsasoft.com>
	<20210112175356.GP4320@momjian.us>
	<66753439-83ae-7be5-6e41-9537a6041a39@dunslane.net>
	<d9f14840-9f6e-183d-f43a-9f9b9e1b6d19@enterprisedb.com>
	<1575064.1615060903@sss.pgh.pa.us>
	<20210430183348.GQ27406@telsasoft.com>
	<a31d593da98da15fc2302a16b3f3b32e491d3e49.camel@vmware.com>

Jacob Champion <pchampion@vmware.com> writes:
> On Fri, 2021-04-30 at 13:33 -0500, Justin Pryzby wrote:
>> I started this.  I don't know if it's compatible with the buildfarm client, but
>> I think any issues maybe can be avoided by using "IF EXISTS".

> Here are the differences I see on a first pass (without putting too
> much thought into how significant the differences are). Buildfarm code
> I'm comparing against is at [1].

I switched the CF entry for this to "Waiting on Author".  It's
been failing in the cfbot for a couple of months, and Jacob's
provided some review-ish comments here, so I think there's
plenty of reason to deem the ball to be in Justin's court.

			regards, tom lane





view thread (36+ messages)  latest in thread

Message-ID: <105345.1631384344@sss.pgh.pa.us>
Permalink:  ../105345.1631384344@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/105345.1631384344@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pchampion@vmware.com, pryzby@telsasoft.com, peter.eisentraut@enterprisedb.com, pgsql-hackers@lists.postgresql.org, buschmann@nidsa.net, andrew@dunslane.net, noah@leadboat.com, tomas.vondra@2ndquadrant.com, bruce@momjian.us, andres@anarazel.de
  Subject: Re: pg_upgrade test for binary compatibility of core data types
  In-Reply-To: <105345.1631384344@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox