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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>
Cc: "David E(dot) Wheeler" <david(at)justatheory(dot)com>, nathandbossart(at)gmail(dot)com, pg(at)bowt(dot)ie, andrew(at)dunslane(dot)net, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date: 2025-10-18 15:14:49
Message-ID: 1957147.1760800489@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Mankirat Singh <mankiratsingh1315(at)gmail(dot)com> writes:
> But if we want a much clearer way based on symbol names, we could use a
> standard per branch suppression file, which the abidiff tool directly
> supports for this purpose[1].

I am strongly against relying on suppression files. I think that
is a very imprecise technology, and it is certainly harder to use
than the "choose a blessed reference point" approach.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Jones 2025-10-18 15:19:30 Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement
Previous Message Srinath Reddy Sadipiralla 2025-10-18 14:17:06 Re: Making pg_rewind faster