| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Gunnar Nick Bluth <gunnar(dot)bluth(at)pro-open(dot)de>, 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 15:49:34 |
| Message-ID: | 202204061549.cunaw3sme425@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-04-06 15:49:59 | Re: [PATCH] pg_stat_toast |
| Previous Message | Andrew Dunstan | 2022-04-06 15:33:37 | Re: SQL/JSON: JSON_TABLE |