Re: Proposed patch for key management

From: Joshua Drake <jd(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Alastair Turner <minion(at)decodable(dot)me>, Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>
Subject: Re: Proposed patch for key management
Date: 2020-12-31 18:41:01
Message-ID: CAJvJg-RF2DdA6ugSCkCDeGnUYYuMHjxnTgDYj7n89H3Vum9WSA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 30, 2020 at 3:47 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:

>
> I will say that if the community feels external-only should be the only
> option, I will stop working on this feature because I feel the result
> would be too fragile to be reliable, and I would not want to be
> associated with it.
>
>
I can say that the people that I work with would prefer an "officially"
supported mechanism from Postgresql.org. The use of a generic API would be
useful for the ecosystem who wants to build on core functionality but
Postgresql should have competent built-in support as well.

JD

>
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua Drake 2020-12-31 18:46:57 Re: Proposed patch for key management
Previous Message Andrew Dunstan 2020-12-31 17:54:07 Re: Buildfarm's cross-version-upgrade tests