From: Tom Lane <tgl@sss.pgh.pa.us>
To: Noah Misch <noah@leadboat.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic
Date: Sat, 14 Oct 2023 22:02:55 -0400
Message-ID: <1991711.1697335375@sss.pgh.pa.us> (raw)
In-Reply-To: <20231015013607.61@rfd.leadboat.com>
References: <E1qroAX-000arw-0A@gemulon.postgresql.org>
<1974777.1697327121@sss.pgh.pa.us>
<20231015000358.2d@rfd.leadboat.com>
<1980111.1697329678@sss.pgh.pa.us>
<20231015013607.61@rfd.leadboat.com>
Noah Misch <noah@leadboat.com> writes:
> On Sat, Oct 14, 2023 at 08:27:58PM -0400, Tom Lane wrote:
>> Well, that's indeed going to be a pain for affected people, but
>> it doesn't seem like a reason to also break installcheck.
> That's right. We don't have a standard that installcheck of v13.N will have
> zero diffs on an initdb from v13.0.
Um ... don't we? I do not recall very many cases where we changed
initial catalog contents at all in a point release, and I don't think
any of those cases intentionally created regression diffs.
> We've got bigger fish to fry.
True, this isn't going to affect many people either way. But
I don't think you've made a good precedent here.
regards, tom lane
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-committers@postgresql.org
Cc: tgl@sss.pgh.pa.us, noah@leadboat.com, pg@bowt.ie, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic
In-Reply-To: <1991711.1697335375@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