Re: [PATCH] pg_stat_toast - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] pg_stat_toast
Date
Msg-id 20220406023435.ynfdeqrl7q4wsqyk@alap3.anarazel.de
Whole thread Raw
In response to Re: [PATCH] pg_stat_toast  ("Gunnar \"Nick\" Bluth" <gunnar.bluth@pro-open.de>)
Responses Re: [PATCH] pg_stat_toast  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

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:
https://www.postgresql.org/message-id/20220405030506.lfdhbu5zf4tzdpux%40alap3.anarazel.de

> 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.


Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: SQL/JSON: JSON_TABLE
Next
From: Andres Freund
Date:
Subject: Re: shared-memory based stats collector - v70