Request a Demo
Home   >   mailing lists

Re: Don't use pq_putmessage in socket comm function - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Don't use pq_putmessage in socket comm function
Date
Msg-id CAHGQGwG0tdzboMzYvLYRDHh3bQFoi47UXpb4AUrVhhqDA4iv5w@mail.gmail.com
Whole thread
In response to Re: Don't use pq_putmessage in socket comm function  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
On Wed, Jul 22, 2026 at 5:30 PM Michael Paquier <michael@paquier.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

pgsql-hackers by date:

Previous
From: Aleksander Alekseev
Date:
Subject: Re: [PATCH] Cover get_json_table_plan() with tests
Next
From: ayoub.kazar@data-bene.io
Date:
Subject: Add support for label conjunction (&) in SQL/PGQ