Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic
Date: 2023-10-15 00:27:58
Message-ID: 1980111.1697329678@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Noah Misch <noah(at)leadboat(dot)com> writes:
> On Sat, Oct 14, 2023 at 07:45:21PM -0400, Tom Lane wrote:
>> Hmm, I'm not sure that that last is a good idea. The upshot of this
>> (because of the opr_sanity.out change) is that "make installcheck"
>> will fail against existing back-branch installations. That seems
>> more likely to cause problems/confusion than the alternative of just
>> depending on the code change.

> I'm way more worried about amcheck failing on all those indexes than I am
> about someone who needs to tweak their installcheck rig.

Well, that's indeed going to be a pain for affected people, but
it doesn't seem like a reason to also break installcheck.

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Noah Misch 2023-10-15 01:36:07 Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic
Previous Message Noah Misch 2023-10-15 00:03:58 Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic