Re: Reorganize GUC structs

Peter Eisentraut <peter@eisentraut.org>

From: Peter Eisentraut <peter@eisentraut.org>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>, Heikki Linnakangas <hlinnaka@iki.fi>, John Naylor <johncnaylorls@gmail.com>
Date: 2025-11-07T15:44:40Z
Lists: pgsql-hackers
On 07.11.25 10:38, Álvaro Herrera wrote:
> On 2025-Nov-07, Peter Eisentraut wrote:
> 
>> @@ -3135,14 +3135,14 @@ parse_and_validate_value(const struct config_generic *record,
>>   					char	   *hintmsg;
>>   
>>   					hintmsg = config_enum_get_options(conf,
>> -													  "Available values: ",
>> -													  ".", ", ");
>> +													  _("Available values: "),
>> +													  _("."), _(", "));
> 
> Hmm, it seems unclear (from the message catalog perspective) what the
> last two strings will be used for, so please add a /* translator */
> comment to each.

Actually, the ", " already exists in the message catalog, so adding a 
comment here might confuse the other site.




Commits

  1. Remove extraneous newlines from guc_parameters.dat

  2. Fix NLS for incorrect GUC enum value hint message

  3. Clean up qsort comparison function for GUC entries

  4. Sort guc_parameters.dat alphabetically by name

  5. Reorganize GUC structs

  6. Change config_generic.vartype to be initialized at compile time

  7. Use designated initializers for guc_tables

  8. Change reset_extra into a config_generic common field

  9. Add some const qualifiers

  10. Modernize some for loops