Re: contrib/pg_stat_tcpinfo

From: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
To: Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: contrib/pg_stat_tcpinfo
Date: 2026-09-23 17:26:47
Message-ID: CAOYmi+kBMHfzFpOJKb2S4oDRuGVBx+aVDtw_jTPwDFFgXyU4Mw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 10, 2025 at 12:35 AM Jakub Wartak
<jakub(dot)wartak(at)enterprisedb(dot)com> wrote:
>
> On Sat, Nov 8, 2025 at 1:18 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> > FWIW, I've needed this many times. Without the TCP information it's very hard
> > to figure out why higher latency connections aren't keeping up - is it packet
> > loss, it it too small network buffers on the sending/receiving side, is it the
> > remote side not keeping up on the CPU level...
>
> Pretty much the same!

+1 (and I wish I had this today, in particular...)

> Still , it is still PoC, and I'm not sure if the community is open to
> accept (or reject it).

I think it's a useful concept.

Thanks,
--Jacob

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rui Zhao 2026-09-23 17:33:31 Re: Race conditions in logical decoding
Previous Message Sami Imseih 2026-09-23 17:21:46 Re: Add REPACK progress phases for logical decoding setup