Date: Tue, 15 Dec 2020 10:17:28 -0500
From: Bruce Momjian <bruce@momjian.us>
To: Michael Paquier <michael@paquier.xyz>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>,
	Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Subject: Re: Proposed patch for key managment
Message-ID: <20201215151728.GD14596@momjian.us>
References: <20201202213814.GG20285@momjian.us>
 <20201214230615.GA14596@momjian.us>
 <X9gL7bD9idE2hoFt@paquier.xyz>
 <20201215031902.GB14596@momjian.us>
 <X9hHoQcZ11pBtgnz@paquier.xyz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <X9hHoQcZ11pBtgnz@paquier.xyz>
User-Agent: Mutt/1.10.1 (2018-07-13)
Precedence: bulk

On Tue, Dec 15, 2020 at 02:20:33PM +0900, Michael Paquier wrote:
> > Uh, I got this code from pg_resetwal.c, which does something similar to
> > pg_altercpass.
> 
> Yeah, that's actually the part where it is a bad idea to just copy
> this pattern.  pg_resetwal should not do that in the long term in my
> opinion, but nobody has come to clean up this stuff.  (- -;)

Glad you asked about this.  It turns out pg_altercpass works fine with
postgres_fe.h, so I will now use that.  pg_resetwal still can't use it
though.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

  The usefulness of a cup is in its emptiness, Bruce Lee