Re: analyze after a database restore? - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: analyze after a database restore?
Date
Msg-id 061601c2decd$e9a14f00$6500a8c0@fhp.internal
Whole thread Raw
In response to analyze after a database restore?  (mlw <pgsql@mohawksoft.com>)
List pgsql-hackers
> Although I suggested doing a single unconditional ANALYZE at the end
> of the script, second thought leads me to think the per-table ANALYZE
> (probably issued right after the table's data-load step) might be
> better.  That way you'd not have any side-effects on already-existing
> tables in the database you are loading to.  OTOH, that way would leave
> the system catalogs un-analyzed, which might be bad.

How about adding an ANALYZE SCHEMA pg_catalog; option :)

Chris




pgsql-hackers by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: [PERFORM] Index File growing big.
Next
From: Alvaro Herrera
Date:
Subject: Re: Brain dump: btree collapsing