| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ANALYZE post-upgrade |
| Date: | 2025-02-26 07:04:08 |
| Message-ID: | CANzqJaDyoFpw5nrTcf8-cpAo_R_QvJTcqRrFNLdxS1zStRRr2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Tue, Feb 25, 2025 at 11:40 PM Edwin UY <edwin(dot)uy(at)gmail(dot)com> wrote:
> Hi,
>
> Just being paranoid here, sorry for a dumb question of sorts.
> The ANALYZE run post upgrade, that doesn't include having to run it on the
> postgres database, does it?
> It is only for the databases that you manually created for your
> application?
>
The postgres database is soooo tiny, an after-pg_upgrade ANALYZE of that
table would take seconds at most, unless you unwisely put user tables in
the database? IOW, don't worry whether or not it gets initially analyzed.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Juan Rincon Gonzalez | 2025-02-26 09:37:08 | Re: Hot Standby setup - collation version mismatch |
| Previous Message | Mahendra Singh | 2025-02-26 05:25:59 | Re: Migrate data from Oracle to EPAS, EPAS to PostgreSQL |