Re: ABI Compliance Checker GSoC Project - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ABI Compliance Checker GSoC Project
Date
Msg-id 1213239.1769696332@sss.pgh.pa.us
Whole thread Raw
In response to Re: ABI Compliance Checker GSoC Project  (Dean Rasheed <dean.a.rasheed@gmail.com>)
Responses Re: ABI Compliance Checker GSoC Project
List pgsql-hackers
Dean Rasheed <dean.a.rasheed@gmail.com> writes:
> OK, baza is now showing the 1 artifact change that I would expect
> (TransitionCaptureState) [1-4]. That should go away after I push my
> change to .abi-compliance-history.

> However, crake is now showing between 4 and 17 artifacts changes
> [5-8]. Apart from the 1 expected failure, the rest appear to have
> nothing to do with any recent commits.

Yeah.  Those look exactly like what I got when I experimentally
installed the headersdir fix without flushing the animal's
cached abidw output for the reference commit, ie they compare
reference-without-headersdir to current-with-headersdir.  So
I think this means that Andrew just forgot that step, and it will
go away by itself when you push the .abi-compliance-history
changes (forcing a rebuild of the cached abidw output).

            regards, tom lane



pgsql-hackers by date:

Previous
From: Anthonin Bonnefoy
Date:
Subject: Re: Auto-tune shared_buffers to use available huge pages
Next
From: Alexander Pyhalov
Date:
Subject: Re: Limit memory usage by postgres_fdw batches