On Thu, Jul 23, 2026 at 10:06 AM Michael Paquier <[email protected]> wrote:
> Done this one, but only on HEAD as the existing code is not broken,
> either.  That's debatable.

Thanks! I agree that this isn't an issue with the current PqCommMethods code.

I'm currently experimenting using a custom PQcommMethods layer to
compress messages, which then use PqCommSocketMethods to forward the
compressed payloads. That's how I've triggered the issue with the
socket_putmessage_noblock calling back compression's putmessage.

Without a similar setup with multiple PQcommMethods layers,
socket_putmessage_noblock using pq_putmessage shouldn't be an issue.

Regards,
Anthonin Bonnefoy


Reply via email to