Re: Convert node test compile-time settings into run-time parameters - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Convert node test compile-time settings into run-time parameters
Date
Msg-id b1173b58-5b73-4bf4-a87e-6792f7b4cff2@eisentraut.org
Whole thread Raw
In response to Re: Convert node test compile-time settings into run-time parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 24.05.24 16:39, Tom Lane wrote:
>>> Maybe not three settings, but a single setting, with multiple values, like
>>> debug_io_direct?
>> Yeah, good idea.  Let's get some more feedback on this before I code up
>> a complicated list parser.
> Kinda doubt it's worth the trouble, either to code the GUC support or
> to use it.  I don't object to having the booleans in a debug build,
> I was just concerned about whether they should exist in production.

Right.  My inclination is to go ahead with the patch as proposed at this 
time.  There might be other ideas for tweaks in this area, but they 
could be applied as new patches on top of this.  The main goal here was 
to do $subject, and without overhead for production builds, and this 
accomplishes that.




pgsql-hackers by date:

Previous
From: Pradeep Kumar
Date:
Subject: rare crash - FailedAssertion snapbuild.c Line: 580
Next
From: Michael Paquier
Date:
Subject: Re: pg_upgrade and logical replication