Re: vacuum analyze after updating from CVS?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: vacuum analyze after updating from CVS?
Date: 2003-07-12 21:13:36
Message-ID: 18561.1058044416@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Bruno Wolff III <bruno(at)wolff(dot)to> writes:
> I have found that at least one query I do gets a poor plan after I update
> from CVS even if I don't need to do an initdb. Sometimes I have done an
> initdb to clear things up; most recently a vacuum analyze did the trick.
> This is a database used read only for web pages that I occasionally
> reload (part of the reload process is to do a vacuum analyze).
> Is this something I should expect? I would think since the stats were
> stored in the database, they would continue to be valid after updating
> the code (unless an initdb was forced).

If you didn't do initdb then I'd not expect pg_statistic to get wiped.
Details please?

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2003-07-12 21:37:10 Re: Insert Updates Deletes on Views; Triggers on System Tables
Previous Message Tom Lane 2003-07-12 21:05:12 Re: [HACKERS] PG crash on simple query, story continues