From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Bandy <bandy(dot)chris(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Allow root ownership of client certificate key |
Date: | 2022-03-02 17:17:34 |
Message-ID: | 5648febc-f46f-4df7-ad07-bbcff0eba8e4@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 3/2/22 08:40, Tom Lane wrote:
> Chris Bandy <bandy(dot)chris(at)gmail(dot)com> writes:
>> On 3/1/22 3:15 AM, Tom Lane wrote:
>>> Anyway, I'd be happier about back-patching if we could document
>>> actual requests to make it work like the server side does.
>
>> PGO runs PostgreSQL 10 through 14 in Kubernetes, and we have to work
>> around this issue when using certificates for system accounts.
>
> Sold then, I'll make it so in a bit.
Thank you! I think the containers community is really going to
appreciate this.
Regards,
-David
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2022-03-02 17:24:24 | Re: pg_stop_backup() v2 incorrectly marked as proretset |
Previous Message | Bharath Rupireddy | 2022-03-02 17:07:43 | Re: pg_walinspect - a new extension to get raw WAL data and WAL stats |