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 230647.1760971159@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()  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
Re: abi-compliance-check failure due to recent changes to pg_{clear,restore}_{attribute,relation}_stats()
List pgsql-hackers
"David E. Wheeler" <david@justatheory.com> writes:
> I’ve now deployed this change (well, a subsequent change that does it better) to baza, so once the
.abi-compliance-historyhas been committed to the rev 18 branch (assuming the format is compatible), it should start
passingagain. 

OK, I pushed a placeholder following Nathan's formatting proposal.
The ABI checker should still complain, because I made it point at
REL_18_0^, which is what I expect we'd do in practice.  After we
see it respond to that, we can move the reference point to where
it needs to be.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_waldump: support decoding of WAL inside tarfile
Next
From: Oleg Tselebrovskiy
Date:
Subject: Re: Proposal for enabling auto-vectorization for checksum calculations