Re: analyze after a database restore?

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "mlw" <pgsql(at)mohawksoft(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: analyze after a database restore?
Date: 2003-02-28 02:05:48
Message-ID: 061601c2decd$e9a14f00$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2003-02-28 02:19:37 Re: Brain dump: btree collapsing
Previous Message Christopher Kings-Lynne 2003-02-28 01:57:43 Re: [PERFORM] Index File growing big.