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

From Alvaro Herrera
Subject Re: [PATCH] pg_stat_toast
Date
Msg-id 202204061549.cunaw3sme425@alvherre.pgsql
Whole thread Raw
In response to Re: [PATCH] pg_stat_toast  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [PATCH] pg_stat_toast  (Robert Haas <robertmhaas@gmail.com>)
Re: [PATCH] pg_stat_toast  ("Gunnar \"Nick\" Bluth" <gunnar.bluth@pro-open.de>)
List pgsql-hackers
On 2022-Apr-06, Robert Haas wrote:

> Now if we're only incurring that overhead when this feature is
> enabled, then in fairness that problem is a lot less of an issue,
> especially if this is also disabled by default. People who want the
> data can get it and pay the cost, and others aren't much impacted.
> However, experience has taught me that a lot of skepticism is
> warranted when it comes to claims about how cheap extensions to the
> statistics system will be.

Maybe this feature should provide a way to be enabled for tables
individually, so you pay the overhead only where you need it and don't
swamp the system with stats for uninteresting tables.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
"Cada quien es cada cual y baja las escaleras como quiere" (JMSerrat)



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON: JSON_TABLE
Next
From: Robert Haas
Date:
Subject: Re: [PATCH] pg_stat_toast