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

Re: analyze after a database restore?

From: "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net>
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-27 18:58:47
Message-ID: 200302271358.47967.darcy@druid.net (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thursday 27 February 2003 13:12, mlw wrote:
> Tom Lane wrote:
> >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?
> [...]
>  From an "ease of use" perspective, it would be one less step.

Why not have pg_dump emit a friendly reminder?

-- 
D'Arcy J.M. Cain <darcy(at){druid|vex}.net>   |  Democracy is three wolves
http://www.druid.net/darcy/                |  and a sheep voting on
+1 416 425 1212     (DoD#0082)    (eNTP)   |  what's for dinner.

In response to

Responses

pgsql-hackers by date

Next:From: Joe ConwayDate: 2003-02-27 19:33:21
Subject: Re: [HACKERS] loading libraries on Postmaster startup
Previous:From: mlwDate: 2003-02-27 18:12:29
Subject: Re: analyze after a database restore?

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