Request a Demo
Home   >   mailing lists

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

From Tom Lane
Subject Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Date
Msg-id 1957147.1760800489@sss.pgh.pa.us
Whole thread Raw
In response to Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()  (Mankirat Singh <mankiratsingh1315@gmail.com>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
Tree view 
Mankirat Singh <mankiratsingh1315@gmail.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

pgsql-hackers by date:

Previous
From: Srinath Reddy Sadipiralla
Date:
Subject: Re: Making pg_rewind faster
Next
From: Jim Jones
Date:
Subject: Re: [PATCH] Add pg_get_trigger_ddl() to retrieve the CREATE TRIGGER statement