From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: Odd problem with performance in duplicate database
Date: Mon, 11 Aug 2003 15:59:09 -0700
Message-ID: <200308111559.09924.josh@agliodbs.com> (raw)
In-Reply-To: <ENEDIMLCODBHILEONAOMAEBNCEAA.pdarley@kinesis-cem.com>
References: <ENEDIMLCODBHILEONAOMAEBNCEAA.pdarley@kinesis-cem.com>
Peter,
> I'm sure that you've thought of this, but it sounds like you may not have
> done an analyze in your new DB.
Yes. Also a VACUUM. Also forcing a REINDEX on the major involved tables.
Also running counts on the pg_* system tables to see if any objects did not
get restored from the backup as compared with the live database.
By everything I can measure, the live database and the test are identical; yet
the test does not think that idx_caseclients_case is very accessable, and the
live database knows it is.
Is this perhaps a bug with ANALYZE statistics in 7.2.4? I know that in that
version I don't have the option of increasing the statistics sampling ...
--
-Josh Berkus
Aglio Database Solutions
San Francisco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com
Subject: Re: Odd problem with performance in duplicate database
In-Reply-To: <200308111559.09924.josh@agliodbs.com>
References: <ENEDIMLCODBHILEONAOMAEBNCEAA.pdarley@kinesis-cem.com> <200308111559.09924.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox