Re: Don't use pq_putmessage in socket comm function

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Don't use pq_putmessage in socket comm function
Date: 2026-07-22 09:15:15
Message-ID: CAHGQGwG0tdzboMzYvLYRDHh3bQFoi47UXpb4AUrVhhqDA4iv5w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 22, 2026 at 5:30 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Yes, that's strange. It seems like a mistake going down to 9.5, as of
> 2bd9e412f92b where socket_putmessage_noblock() has been introduced,
> leaving the pq_putmessage() around.
>
> Thoughts or opinions?

Agreed. The proposed change looks correct to me.

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message ayoub.kazar 2026-07-22 09:31:48 Add support for label conjunction (&) in SQL/PGQ
Previous Message Aleksander Alekseev 2026-07-22 09:06:23 Re: [PATCH] Cover get_json_table_plan() with tests