Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sami Imseih <samimseih(dot)pg(at)gmail(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, aleksander(at)timescale(dot)com
Subject: Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress
Date: 2026-09-10 17:14:55
Message-ID: 915102.1789060495@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sami Imseih <samimseih(dot)pg(at)gmail(dot)com> writes:
> On Thu, Sep 10, 2026 at 9:30 AM Nathan Bossart <nathandbossart(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bryan Green 2026-09-10 17:21:12 Re: COPY FROM with RLS
Previous Message Sami Imseih 2026-09-10 17:09:00 Re: Rename PqMsg_Progress to PqMsg_ParallelWorkerProgress