Re: Consistent coding for the naming of LR workers - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Consistent coding for the naming of LR workers
Date
Msg-id e2b3cdb7-adb5-6c2a-d973-3265adcef9bb@eisentraut.org
Whole thread Raw
In response to Re: Consistent coding for the naming of LR workers  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: Consistent coding for the naming of LR workers
List pgsql-hackers
On 21.06.23 09:18, Alvaro Herrera wrote:
> That is a terrible pattern in relatively new code.  Let's get rid of it
> entirely rather than continue to propagate it.
> 
>> So, I don't think it is fair to say that these format strings are OK
>> for the existing HEAD code, but not OK for the patch code, when they
>> are both the same.
> 
> Agreed.  Let's remove them all.

This is an open issue for PG16 translation.  I propose the attached 
patch to fix this.  Mostly, this just reverts to the previous wordings. 
(I don't think for these messages the difference between "apply worker" 
and "parallel apply worker" is all that interesting to explode the 
number of messages.  AFAICT, the table sync worker case wasn't even 
used, since callers always handled it separately.)

Attachment

pgsql-hackers by date:

Previous
From: Pavel Luzanov
Date:
Subject: Re: psql: Add role's membership options to the \du+ command
Next
From: Daniel Gustafsson
Date:
Subject: Re: Testing autovacuum wraparound (including failsafe)