Re: MPTCP - multiplexing many TCP connections through one socket to get better bandwidth

From: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: MPTCP - multiplexing many TCP connections through one socket to get better bandwidth
Date: 2026-08-17 08:19:50
Message-ID: CAKZiRmyPM=VqRXF4hYYnVmZEJnJkf5X6TaGKk446b=sh1QXscg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 13, 2026 at 9:59 PM Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:
>
> I like the idea a lot. Have not tested yet, but the patch looks okay as a POC. I'm wondering if rather than a run-time check for IPPROTO_MCP in src/backend/libpq/pqcomm.c, we shouldn't check right away as soon as it is enabled via a guc check - see check_bonjour as a good example.

Hi Greg, thanks for taking a look. I've attached v3 that added
check_listen_mptcp() (GUC check) that enhanced the situation just as You
have indicated.

-J.

Attachment Content-Type Size
v3-0001-Add-MPTCP-protocol-support-to-server-and-libpq-on.patch text/x-patch 9.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message 陈列行 2026-08-17 08:28:51 PostgreSQL does not propagate empty inputs through INTERSECT and EXCEPT
Previous Message 陈列行 2026-08-17 08:17:55 Semantically redundant OR FALSE prevents IN-subquery pull-up and causes a slower SubPlan