Re: [PoC] Federated Authn/z with OAUTHBEARER - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: [PoC] Federated Authn/z with OAUTHBEARER
Date
Msg-id CAOYmi+=0huteqRBa_1ZMdKF9nPxsjOeMk=qzJiQVkeB_T3UKSQ@mail.gmail.com
Whole thread Raw
In response to Re: [PoC] Federated Authn/z with OAUTHBEARER  (Christoph Berg <myon@debian.org>)
List pgsql-hackers
On Fri, Apr 25, 2025 at 2:03 AM Christoph Berg <myon@debian.org> wrote:
> My point is that we should be trying to change the ABI-as-coded-in-the-
> filename as rarely as possible.

I agree, but I'm also trying to say I can't unilaterally declare
pieces of our internal structs to be covered by an ABI guarantee.
Maybe the rest of the ABI will never change because it'll be perfect,
but I point to the immediately preceding thread as evidence against
the likelihood of perfection on the first try. I'm trying to build in
air bags so we don't have to regret a mistake.

> Then side-by-side should not be required.

It's still required _during_ an ABI bump, though, if you don't want
things to break. Right?

--Jacob



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: gcc 15 "array subscript 0" warning at level -O3
Next
From: Matthias van de Meent
Date:
Subject: [SP-]GiST IOS visibility bug (was: Why doens't GiST require super-exclusive lock)