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

From Alvaro Herrera
Subject Re: analyze after a database restore?
Date
Msg-id 20030227224411.GA10724@dcc.uchile.cl
Whole thread Raw
In response to Re: analyze after a database restore?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Thu, Feb 27, 2003 at 03:12:36PM -0500, Tom Lane wrote:

> 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.

Huh... is there a way to analyze a specific schema?  Maybe that can
solve the problem of system catalogs being left un-analyzed, by having
pg_dump emit an "ANALYZE SCHEMA pg_catalog" or something.

-- 
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)
"La libertad es como el dinero; el que no la sabe emplear la pierde" (Alvarez)


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Free-space-map management thoughts
Next
From: Justin Clift
Date:
Subject: Re: analyze after a database restore?