| From: | Robert Treat <rob(at)xzilla(dot)net> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org> |
| Cc: | VASUKI M <vasukianand0119(at)gmail(dot)com>, Ilia Evdokimov <ilya(dot)evdokimov(at)tantorlabs(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Subject: | Re: Optional skipping of unchanged relations during ANALYZE? |
| Date: | 2026-01-22 19:42:52 |
| Message-ID: | CAJSLCQ2ZTLng_4vF9O74oxaOg_cAxD6=ixLMoW_+5CxCkNtXrA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 21, 2026 at 4:44 AM Christoph Berg <myon(at)debian(dot)org> wrote:
>
> Re: VASUKI M
> > VACUUM(SMART);
>
> IMHO it was a historical mistake to combine VACUUM and ANALYZE into a
> single command. We should not add any more options on that
> combination. If people want to pass options to ANALYZE, they should
> call ANALYZE and not VACUUM.
>
I don't know if I go that far, but if you are saying that you dont
think "smart analyze" should be an option for vacuum runs, I can get
onboard with that. We don't really know what any given vacuum run will
do with regards to the table, but if we are shuffling data / storage
around, it probably makes sense to update statistics info along the
way.
Robert Treat
https://xzilla.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-01-22 19:46:37 | Re: warning: dereferencing type-punned pointer |
| Previous Message | Joao Foltran | 2026-01-22 19:41:13 | Re: [BUG] [PATCH] Allow physical replication slots to recover from archive after invalidation |