Date: Tue, 8 Apr 2025 13:15:47 -0400
From: Bruce Momjian <bruce@momjian.us>
To: Jacob Champion <jacob.champion@enterprisedb.com>
Cc: Wolfgang Walther <walther@technowledgy.de>,
	Daniel Gustafsson <daniel@yesql.se>,
	Christoph Berg <myon@debian.org>,
	Andres Freund <andres@anarazel.de>,
	Peter Eisentraut <peter@eisentraut.org>,
	Tom Lane <tgl@sss.pgh.pa.us>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	Thomas Munro <thomas.munro@gmail.com>,
	Nazir Bilal Yavuz <byavuz81@gmail.com>,
	Antonin Houska <ah@cybertec.at>
Subject: Re: [PoC] Federated Authn/z with OAUTHBEARER
Message-ID: <Z_VZw6H_JxxAlXnu@momjian.us>
References: <Z_Uzde7a1lCFaqfW@momjian.us>
 <CAOYmi+mrYnuwMEnpYWA4FWFtDCe4rMKavDrKQPpV43u=zmR8Xg@mail.gmail.com>
 <96b5b38b-2fac-409f-b922-f7fd653bf847@technowledgy.de>
 <CAOYmi+m-q8VOPsFxB3D-CWf-T057h4XLqVPvCTudXyAj7-9vpA@mail.gmail.com>
 <bf7c3396-a9a2-4df7-aabd-6fed387e027b@technowledgy.de>
 <CAOYmi+mn_xhkQEyS5KG3zoSOrvskVx8mhD8x_Z+0LL9PaZo1gQ@mail.gmail.com>
 <18f84e6a-41cf-4313-8bea-6007868dd05a@technowledgy.de>
 <CAOYmi+=fhzr4Mm5MVwFa+pmwn-uSrPpjfYNfQ9EPBLh8xPV3cA@mail.gmail.com>
 <214ec3cc-7531-4360-8103-663581d2149f@technowledgy.de>
 <CAOYmi+m2URt8OcST0Lu5=xd=tzgHvCQS_87HDhM1+JPDBbRVbA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAOYmi+m2URt8OcST0Lu5=xd=tzgHvCQS_87HDhM1+JPDBbRVbA@mail.gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/Z_VZw6H_JxxAlXnu%40momjian.us>
Precedence: bulk

On Tue, Apr  8, 2025 at 10:13:46AM -0700, Jacob Champion wrote:
> On Tue, Apr 8, 2025 at 10:10 AM Wolfgang Walther
> <walther@technowledgy.de> wrote:
> > And if that means making libpq modular at run-time, then this should be planned and built with all deps, and other use-cases (like static linking) in mind - and not like it is right now.
> 
> I think that'd be neat in concept, but specifically this thread is
> discussing a PG18 open item. For future releases, if we're happy with
> how Curl gets split out, maybe that would be fuel for other
> delay-loaded client dependencies. I'm not sure.

Well, if we think we are going to do that, it seems we would need a
different architecture than the one being proposed for PG 18, which
could lead to a lot of user/developer API churn.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Do not let urgent matters crowd out time for investment in the future.