Horton

Re: Extended test coverage and docs for SSL passphrase commands

Daniel Gustafsson <daniel@yesql.se>

View thread View on postgr.es
From: Daniel Gustafsson <daniel@yesql.se>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Peter Eisentraut <peter@eisentraut.org>, Postgres hackers <pgsql-hackers@lists.postgresql.org>, Chao Li <li.evan.chao@gmail.com>
Date: 2025-11-23T19:56:35Z
Lists: pgsql-hackers

Attachments

> On 22 Nov 2025, at 14:00, Álvaro Herrera <alvherre@kurilemu.de> wrote:
> 
> On 2025-Nov-21, Daniel Gustafsson wrote:
> 
>> The attached v2 adds a GUC debug_exec_backend which can be used to get the
>> state of the running cluster,
> 
> Nice idea.
> 
> I think the parallel to debug_assertions is not perfect, because you can
> turn off debug_assertions in a server built with them included, but you
> cannot turn off EXEC_BACKEND.

debug_assertions cannot be disabled anymore, since 3bdcf6a5a755.

>  This says we shouldn't name the symbol
> with the DEFAULT word: it should just be "EXEC_BACKEND_ENABLED".

Regardless, I totally agree with that, fixed in the attached along with the
review comments from upthread.

--
Daniel Gustafsson

Commits

  1. doc: Clarify passphrase command reloading on Windows

  2. ssl: Add connection and reload tests for key passphrases

  3. Add GUC to show EXEC_BACKEND state