Re: [PATCH] Automatic client certificate selection support for libpq v1

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Seth Robertson <in-pgsql-hackers(at)baka(dot)org>, Robin Haberkorn <haberkorn(at)b1-systems(dot)de>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Automatic client certificate selection support for libpq v1
Date: 2025-03-31 16:52:49
Message-ID: CAOYmi+k9c=mBXOB_F0Q4AORA-p4_E8XHtqEmRn7WKMbLGjSeKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Mar 31, 2025 at 9:01 AM Seth Robertson
<in-pgsql-hackers(at)baka(dot)org> wrote:
> Third, the only real use case where this feature would be critical is
> a client which needs to have connections to two different PostgreSQL
> servers at the same time. Those applications are likely fairly rare
> and doing custom programming to support different filenames would
> likely be warranted.

Can this be handled well enough with a service file?

> Given the lack of "me too" or "+1" posts over the past 16 years, I
> suspect there may be features with higher user benefit. I would not
> cry if it gets removed.

Yeah, at least not without a solid use case. (If anyone does feel
motivated to pick it up, be aware of the server-side SNI work [1].
It'd be nice if the two halves were complementary -- or at minimum,
not clashing with each other.)

Thanks!
--Jacob

[1] https://postgr.es/m/1C81CD0D-407E-44F9-833A-DD0331C202E5%40yesql.se

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-03-31 16:55:45 Re: Reduce "Var IS [NOT] NULL" quals during constant folding
Previous Message Nazir Bilal Yavuz 2025-03-31 16:49:25 Re: Add pg_buffercache_evict_all() and pg_buffercache_mark_dirty[_all]() functions