| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | "David E(dot) Wheeler" <david(at)justatheory(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Mankirat Singh <mankiratsingh1315(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: ABI Compliance Checker GSoC Project |
| Date: | 2026-01-29 14:18:52 |
| Message-ID: | 1213239.1769696332@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Pyhalov | 2026-01-29 14:24:15 | Re: Limit memory usage by postgres_fdw batches |
| Previous Message | Anthonin Bonnefoy | 2026-01-29 14:10:57 | Re: Auto-tune shared_buffers to use available huge pages |