Re: [PATCH] pg_stat_toast

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Gunnar \"Nick\" Bluth" <gunnar(dot)bluth(at)pro-open(dot)de>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>
Subject: Re: [PATCH] pg_stat_toast
Date: 2022-04-06 02:34:35
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2022-04-06 00:08:13 +0200, Gunnar "Nick" Bluth wrote:
> AFAICT, Andres' work is more about the structure (e.g.
> 13619598f1080d7923454634a2570ca1bc0f2fec). Or I've missed something...?

That was just the prep work... I'm about to send slightly further polished
version, but here's the patchset from yesterday:

> The attached v11 incorporates the latest changes in the area, btw.
> Anyway, my (undisputed up to now!) understanding still is that only
> backends _looking_ at these stats (so, e.g., accessing the pg_stat_toast
> view) actually read the data. So, the 10-15% more space used for pg_stat
> only affect the stats collector and _some few_ backends.

It's not so simple. That stats collector constantly writes these stats out to
disk. And disk bandwidth / space is of course a shared resource.


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-04-06 03:00:08 Re: shared-memory based stats collector - v70
Previous Message Andres Freund 2022-04-06 02:21:18 Re: SQL/JSON: JSON_TABLE