Re: Reorganize GUC structs - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Reorganize GUC structs
Date
Msg-id 222481bd-ce00-4957-9789-b56f2398d930@eisentraut.org
Whole thread Raw
In response to Re: Reorganize GUC structs  (Álvaro Herrera <alvherre@kurilemu.de>)
List pgsql-hackers
On 14.11.25 12:00, Álvaro Herrera wrote:
> On 2025-Nov-12, Peter Eisentraut wrote:
> 
>> Well, that's the one, but the code actually looks like this now:
>>
>>      while ((i = bms_next_member(atts, i)) >= 0)
>>      {
>>          attcnt++;
>>          if (attcnt > 1)
>>              appendStringInfoString(&attsbuf, _(", "));
>>
>>          appendStringInfo(&attsbuf, _("\"%s\""), remoterel->attnames[i]);
>>      }
>>
>> The catalog entries you are showing appear to be from pre-PG18.
> 
> Ah, right.
> 
>> There are also similar instances in ExecBuildSlotValueDescription() that are
>> not marked up for gettext but perhaps should be.  There might be others, and
>> I would expect more like this to appear over time, as people like to add
>> more detail like this to diagnostics messages.
> 
> Sure.
> 
>> Do you have a suggestion what kind of comment to attach there?
> 
> I would say "This is a separator in a list of entity names."  We don't
> need to be specific as to what kind of entity it is, I think.

Ok, committed that way.




pgsql-hackers by date:

Previous
From: Maciek Sakrejda
Date:
Subject: Re: Add mode column to pg_stat_progress_vacuum
Next
From: Bertrand Drouvot
Date:
Subject: Re: Consistently use the XLogRecPtrIsInvalid() macro