Re: ABI Compliance Checker GSoC Project

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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-24 21:20:32
Message-ID: 2CEFC7F6-4D97-4078-97AB-AEF8CAE287A2@justatheory.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jan 24, 2026, at 12:54, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> 2. When installing this change into an active BF member, you'd better
> blow away the abicheck.$animal cache tree, else you'll have a mess
> from cached trees not having been analyzed with the same options.
> (I experimented and indeed got some very strange ABI-diff complaints
> when I hadn't done that.)

I’ve applied this change to baza, and after a couple false starts, it seems to be sending OKs. I did have to delete every directory except for `pgmirror.git`.

D

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Geoghegan 2026-01-24 21:21:48 Re: Buffer locking is special (hints, checksums, AIO writes)
Previous Message Tom Lane 2026-01-24 21:11:47 Re: Buffer locking is special (hints, checksums, AIO writes)