Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Fri, 28 Feb 2003 10:05:48 +0800
- Message-id: <061601c2decd$e9a14f00$6500a8c0@fhp.internal> <text/plain>
> 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
- References:
- analyze after a database restore?
- From: mlw
- Re: analyze after a database restore?
- From: Tom Lane
- Re: analyze after a database restore?
- From: mlw
- Re: analyze after a database restore?
- From: Tom Lane
- analyze after a database restore?
- Prev by Date: Re: [PERFORM] Index File growing big.
- Next by Date: Re: Brain dump: btree collapsing
- Previous by thread: Re: analyze after a database restore?
- Next by thread: Re: analyze after a database restore?
- Indexes: