Re: Extended test coverage and docs for SSL passphrase commands

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Extended test coverage and docs for SSL passphrase commands
Date: 2025-11-22 13:00:55
Message-ID: 202511221253.j6m7vw6k5udj@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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. This says we shouldn't name the symbol
with the DEFAULT word: it should just be "EXEC_BACKEND_ENABLED". The
value already cannot be changed, which is good, and there are tests for
this behavior of PGC_INTERNAL gucs in src/test/modules/unsafe_tests/sql/guc_privs.sql,
so I think we don't need anything additional.

--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"Once again, thank you and all of the developers for your hard work on
PostgreSQL. This is by far the most pleasant management experience of
any database I've worked on." (Dan Harris)
http://archives.postgresql.org/pgsql-performance/2006-04/msg00247.php

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2025-11-22 13:07:36 Re: another autovacuum scheduling thread
Previous Message Mihail Nikalayeu 2025-11-22 12:52:17 Re: isolation tester limitation in case of multiple injection points in a single command