Feedback-ID: i131946ab:Fastmail
Message-ID: <9de74f8d-fbf4-63d9-7bcb-b9c27edf8b73@enterprisedb.com>
Date: Tue, 31 Jan 2023 10:59:10 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.6.1
Subject: Re: [PoC] Let libpq reject unexpected authentication requests
Content-Language: en-US
To: Jacob Champion <jchampion@timescale.com>,
 Michael Paquier <michael@paquier.xyz>
Cc: "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
 "David G. Johnston" <david.g.johnston@gmail.com>
References: <ebf31cf7-b0af-7407-ada2-dda6d2767ba0@enterprisedb.com>
 <CAAWbhmg5ddYa=5niqvb4vY7-tpWc2Dj7e=-cNT+WZ64s8V_hVQ@mail.gmail.com>
 <CAAWbhmgOuheFzozhej0HHXJ6wi3Vu73kLrtvD6p9=mJOGOMEfw@mail.gmail.com>
 <914a0125-3dfb-920f-51b6-8d44a8edbdd2@enterprisedb.com>
 <CAAWbhmiRxVNsfaq8DLgxoAh2TBu1SthP9jycutXBz32Z2k80pw@mail.gmail.com>
 <949f1c20-771c-aef7-058f-2c10885db955@enterprisedb.com>
 <CAAWbhmimxNiGMDHju7FsEtem4Rmk1enQ_-ypenjkTQnNPLouMA@mail.gmail.com>
 <8e2e5fb6-8225-de8a-b0f9-178c27402367@enterprisedb.com>
 <d192cc5f-e023-fed5-d82c-dc4fb54773c2@timescale.com>
 <CAAWbhmgjs6kSm1n25a-+ZKOb5QnEzxerMfcmML_rXz2JTKvrpw@mail.gmail.com>
 <Y3SMDoHfS8sy2wwW@paquier.xyz>
 <CAAWbhmixDLmLMNUcMgCGYbG_z85umzUAD_6v=9bZHvxsjnHLpA@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
In-Reply-To: 
 <CAAWbhmixDLmLMNUcMgCGYbG_z85umzUAD_6v=9bZHvxsjnHLpA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/9de74f8d-fbf4-63d9-7bcb-b9c27edf8b73%40enterprisedb.com>
Precedence: bulk

On 16.11.22 18:26, Jacob Champion wrote:
> On Tue, Nov 15, 2022 at 11:07 PM Michael Paquier <michael@paquier.xyz> wrote:
>> I am beginning to look at the last version proposed, which has been
>> marked as RfC.  Does this patch need a refresh in light of a9e9a9f and
>> 0873b2d?  The changes for libpq_append_conn_error() should be
>> straight-forward.
> 
> Updated in v13, thanks!

What is the status of this patch set?  Michael had registered himself as 
committer and then removed himself again.  So I hadn't been paying much 
attention myself.  Was there anything left to discuss?