Skip site navigation (1) Skip section navigation (2)

Re: analyze after a database restore?

From: mlw <pgsql(at)mohawksoft(dot)com>
To: 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-27 18:12:29
Message-ID: 3E5E550D.3090305@mohawksoft.com (view raw or flat)
Thread:
Lists: pgsql-hackers

Tom Lane wrote:

>mlw <pgsql(at)mohawksoft(dot)com> writes:
>  
>
>>Should pg_dump appened an ANALYZE for each table?
>>    
>>
>
>A single ANALYZE at the end of the script would be sufficient.  I'm not
>sure that pg_dump should do this automatically though.  If you're not
>done restoring then it's mostly a waste of cycles, and how is pg_dump to
>know that?
>
>I do note that the docs are rather stingy with this important bit of
>knowhow :-(  Neither of the obvious places that I looked in (pg_dump
>reference page and admin guide's backup/restore chapter) mention the
>need to issue an ANALYZE after completing a restore.  I'm pretty sure it
>is mentioned *somewhere* ;-) ... but it needs to be more prominent.
>  
>
While these are all comforting points, I *know* about analyze and I 
occasionally forget. It just seems like a nessisary step after restoring 
a backup. Conceptually, one could consider it just as important as an 
index, i.e. the system will perform poorly without it.

 From an "ease of use" perspective, it would be one less step.


In response to

Responses

pgsql-hackers by date

Next:From: D'Arcy J.M. CainDate: 2003-02-27 18:58:47
Subject: Re: analyze after a database restore?
Previous:From: Rod TaylorDate: 2003-02-27 18:01:09
Subject: Re: analyze after a database restore?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group