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

From Robert Haas
Subject Re: [PATCH] pg_stat_toast
Date
Msg-id CA+TgmoYPaOHcThzE5dKuyvVr_UcWyPfqsAX1hLXTrpp5_GX1rA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] pg_stat_toast  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
On Wed, Apr 6, 2022 at 11:49 AM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> 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.

Maybe. Or maybe once Andres finishes fixing the stats collector the
cost goes down so much that it's just not a big issue any more. I'm
not sure. For me the first question is really around how useful this
data really is. I think we can take it as given that the data would be
useful to Gunnar, but I can't think of a situation when it would have
been useful to me, so I'm curious what other people think (and why).

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: SQL/JSON: JSON_TABLE
Next
From: Greg Stark
Date:
Subject: Last day of commitfest