Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress
Date
Msg-id 915102.1789060495@sss.pgh.pa.us
Whole thread
In response to Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress  (Sami Imseih <samimseih.pg@gmail.com>)
Responses Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress
List pgsql-hackers
Sami Imseih <samimseih.pg@gmail.com> writes:
> On Thu, Sep 10, 2026 at 9:30 AM Nathan Bossart <nathandbossart@gmail.com> wrote:
>> All of the options I've seen listed in this thread so far involve changing
>> the part after the PqMsg_ prefix, but given we now have PqReplMsg_ and
>> PqBackupMsg_, I'm thinking it'd be better to give parallel worker messages
>> their own prefix.  That seems to act as a sort of class or namespace for
>> the message.  Maybe something like PqParallelMsg_Progress would work here.

> I think PqParallelMsg_Progress makes sense. The attached does this.

+1

            regards, tom lane



pgsql-hackers by date:

Previous
From: Sami Imseih
Date:
Subject: Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress
Next
From: Bryan Green
Date:
Subject: Re: COPY FROM with RLS