| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Murthy Nunna <mnunna(at)fnal(dot)gov> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_dump -Are statistics saved? |
| Date: | 2023-11-28 06:55:23 |
| Message-ID: | 1bb4707116e574187d2c5c445ddf656663858303.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Mon, 2023-11-27 at 19:45 -0500, Tom Lane wrote:
> Murthy Nunna <mnunna(at)fnal(dot)gov> writes:
>
>
> > If not, is it necessary to run ANALYZE after pg_restore?
>
> That has always been necessary after a dump/restore, and still is.
> The pg_dump man page makes this clear enough, I should think:
>
> The dump file produced by pg_dump does not contain the statistics used
> by the optimizer to make query planning decisions. Therefore, it is
> wise to run ANALYZE after restoring from a dump file to ensure optimal
> performance; see Section 25.1.3 and Section 25.1.6 for more
> information.
If you are not pressed for time, you can wait until autovacuum gets around
to calculating the statistics automatically.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ROHIT SACHDEVA | 2023-11-28 08:38:15 | Related to Foreign Table Accessing |
| Previous Message | Laurenz Albe | 2023-11-28 06:53:02 | Re: idle in transaction |