On Sat, Nov 8, 2025 at 1:18 AM Andres Freund wrote:
Hi Andres!
>> But maybe it's very useful in practice, don't know.
> 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
On Sat, Nov 8, 2025 at 12:17 AM Tomas Vondra wrote:
Hi Tomas, thanks for responding!
> On 11/7/25 11:36, Jakub Wartak wrote:
> > On Mon, Nov 3, 2025 at 3:09 PM Jakub Wartak
> > wrote:
> >>
> >> Attached is pg_stat_tcpinfo, an heavy work in progress, Linux-only
> >> netstat/ss-like extension for
Hi,
On 2025-11-08 00:17:30 +0100, Tomas Vondra wrote:
> On 11/7/25 11:36, Jakub Wartak wrote:
> > On Mon, Nov 3, 2025 at 3:09 PM Jakub Wartak
> > wrote:
> >>
> >> Attached is pg_stat_tcpinfo, an heavy work in progress, Linux-only
> >> netstat/ss-like extension for showing detailed information abo
On 11/7/25 11:36, Jakub Wartak wrote:
> On Mon, Nov 3, 2025 at 3:09 PM Jakub Wartak
> wrote:
>>
>> Attached is pg_stat_tcpinfo, an heavy work in progress, Linux-only
>> netstat/ss-like extension for showing detailed information about TCP
>> connections based on information from the kernel itself.
25 14:57:52 +0100
Subject: [PATCH v2] pg_stat_tcpinfo
---
contrib/Makefile |1 +
contrib/meson.build |1 +
contrib/pg_stat_tcpinfo/Makefile | 21 +
contrib/pg_stat_tcpinfo/meson.build | 25 +
...
ke first to
stabilize the outputs/naming/code first.
5. [security] Should this be available to pg_monitor/pg_read_all_stats
or just to superuser?
6. [security] Should this return info about all TCP connections or
just the UID of the postmaster?
-J.
From c7990c216caf7c066381577efce097789a7fbb83 Mon Sep 17
