Re: Proposal: Document ABI Compatibility

From: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Proposal: Document ABI Compatibility
Date: 2024-06-12 15:04:22
Message-ID: 3F0995FD-3872-4AA6-97B4-B27E7EC64450@justatheory.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jun 12, 2024, at 10:47, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> What I think would be useful to document is our usual practices e.g.
> adding new struct members at the end of structs, trying to avoid
> changing public function signatures. If we document promises to
> extension authors, I don't know how much difference that will make:
> we'll probably end up needing to violate them at some point for one
> reason or another.

I think that’s fine if there is some sort of notification process. The policy I drafted upthread starts with making sure the such a break is mentioned in the release notes.

> But if we document what committers should do, then
> we might do better than we're now, because committers will be more
> likely to do it right, and extension authors can also read those
> instructions to understand what our practices are.

Yes, this, thank you!

D

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Imran Zaheer 2024-06-12 15:12:51 Re: Windows: openssl & gssapi dislike each other
Previous Message Nathan Bossart 2024-06-12 15:02:12 Re: Remove dependence on integer wrapping