| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Antonin Houska <ah(at)cybertec(dot)at>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PoC] Federated Authn/z with OAUTHBEARER |
| Date: | 2025-02-24 15:10:14 |
| Message-ID: | dfybm6iyxcsq3kuwx2xpv2thjh2fwkuy4vxbzahb7ntrtuo3ex@gvg2zqsx3d5d |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-02-24 15:48:13 +0100, Daniel Gustafsson wrote:
> > On 24 Feb 2025, at 15:41, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
> > I notice that 001_server.pl contains this:
> >
> > if ($ENV{with_python} ne 'yes')
> > {
> > plan skip_all => 'OAuth tests require --with-python to run';
> > }
> >
> > and various other things that insist on this. But I think all we should need is for Python to be present, whether or not we are building plpython.
>
> Agreed. Right now the --with-python check is what runs PGAC_PATH_PYTHON but
> maybe there is value in separating this going forward into a) have python; b)
> have python and build plpython?
FWIW, For other things we need in tests, e.g. gzip, we don't actually use a
configure test. I think we could do the same for the python commandline
binary.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2025-02-24 15:13:27 | Re: Fix assert failure when decoding XLOG_PARAMETER_CHANGE on primary |
| Previous Message | Andres Freund | 2025-02-24 14:54:22 | Re: Statistics Import and Export |