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

From David E. Wheeler
Subject Re: ABI Compliance Checker GSoC Project
Date
Msg-id F3F86A0B-B56B-4F6D-8716-1E88F9742129@justatheory.com
Whole thread Raw
In response to Re: ABI Compliance Checker GSoC Project  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: ABI Compliance Checker GSoC Project
List pgsql-hackers
On Jul 13, 2025, at 15:02, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> On reflection, assuming that this is being run by one or more
> buildfarm animals, there are not likely to be so many commits
> between runs that it'll be hard to assign blame after a breakage.
> So I'm not convinced that we need to build the logic you describe.

Fair. Better to start simple and add something like this later if it’s a PITA without it.

> Alternatively, does git have any kind of metadata that isn't
> a tag but acts sort of like one?  The fact that you cannot
> move or remove a tag once pushed could come back to bite us
> if we start using them for this purpose.

Notes?

  https://git-scm.com/docs/git-notes

Best,

David


Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: ABI Compliance Checker GSoC Project
Next
From: Melanie Plageman
Date:
Subject: Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access)