Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date: 2025-10-30 00:49:35
Message-ID: A067B3A3-1CB8-44CC-A695-C5D4EDDE847A@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Oct 29, 2025, at 19:52, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I'm asking to remove complexity, not add more. The buildfarm client
> should not be checking either branch names or git tags to control
> this, when we have a perfectly good convention about the existence
> of .abi-compliance-history to control it.

We can remove the branch check, of course, but then you would have to maintain .abi-compliance-history in master, no?

D

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Arne Roland 2025-10-30 01:23:22 Re: apply_scanjoin_target_to_paths and partitionwise join
Previous Message David Rowley 2025-10-30 00:49:19 Re: Use BumpContext contexts for TupleHashTables' tablecxt