| 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 02:02:55 |
| Message-ID: | 1991711.1697335375@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 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2023-10-15 17:51:00 | Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic |
| Previous Message | Noah Misch | 2023-10-15 01:36:07 | Re: pgsql: Dissociate btequalimage() from interval_ops, ending its deduplic |