Re: Require SSL connection to postgres for oauth

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Subject: Re: Require SSL connection to postgres for oauth
Date: 2026-11-06 17:44:07
Message-ID: CAN4CZFNnPhmd3-oLKqU87ktCsBNM9u3j6RDxdfbrnqYonThjow@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, 06 Nov 2026, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> The attached .txt
> (intentionally not a .diff or .patch since I didn't re-send your full patchset)
> massages your 0001 to make it more consistent with the rest of the
> documentation.

Thanks, it looks good to me.

> For v19 I don't see it as
> a realistic change (and I think it was too late even when initially raised,
> even though it was a lot earlier in the cycle than now), but hopefully we can
> raise the bar in v20.

Yes, when I originally submitted the thread I thought this was a
bug/oversight as I didn't find any mention of it being intentional.
Since it was intentional, it was definitely too late in June. I simply
kept all 3 parts there so that they don't get forgotten, as I think
0003 should be a good improvement without breaking any use cases.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-11-06 18:17:41 Re: Require SSL connection to postgres for oauth
Previous Message Prashant Chinnam 2026-11-06 17:34:46 Re: extension_control_path: ignore empty elements and deduplicate directories