Horton

Re: Extended test coverage and docs for SSL passphrase commands

Álvaro Herrera <alvherre@kurilemu.de>

View thread View on postgr.es
From: Álvaro Herrera <alvherre@kurilemu.de>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Peter Eisentraut <peter@eisentraut.org>, Postgres hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-11-12T17:47:36Z
Lists: pgsql-hackers 
On 2025-Nov-12, Daniel Gustafsson wrote:

> As far as I know the only way to programmatically learn that from the Perl
> testcode would be to check for the presence of the CONFIG_EXEC_PARAMS file in
> $self->data_dir, which should be easy enough to do.  Do you know of a better
> way?

We have check_pg_config(), which reads pg_config.h.  For EXEC_BACKEND
you need pg_config_manual.h, but I think you could go roughly in the
same direction ... for instance you could add an argument to
check_pg_config() to say which file to read -- though I think the
easiest is to read both files always and return the grep count in both.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
Officer Krupke, what are we to do?
Gee, officer Krupke, Krup you! (West Side Story, "Gee, Officer Krupke")

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