Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 9AF7C4765E6 for ; Mon, 23 Sep 2002 22:13:30 -0400 (EDT) Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (Postfix) with ESMTP id 08CF14765DE for ; Mon, 23 Sep 2002 22:13:30 -0400 (EDT) Received: from [66.219.92.2] (HELO chocolate-mousse) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.5.9) with ESMTP id 1658368; Mon, 23 Sep 2002 19:13:33 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Aaron Held Subject: Re: Performance w/ multiple WHERE clauses Date: Mon, 23 Sep 2002 19:14:52 -0700 X-Mailer: KMail [version 1.4] Cc: Chris Ruprecht , pgsql-sql@postgresql.org References: <5.1.1.6.2.20020918111926.00a82058@mail.nashlinux.com> <200209201455.30054.josh@agliodbs.com> <3D8F17B5.60902@MetroNY.com> In-Reply-To: <3D8F17B5.60902@MetroNY.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200209231914.52643.josh@agliodbs.com> X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/286 X-Sequence-Number: 9563 Aaron, > This database gets a monthly update and it read only until the next=20 > update. I ANALYZE once after each update. Since the data does not=20 > change I should not need to ANALYZE again afterwards. Actually, if the database is read-only between updates, you should: ANALYZE VACUUM FULL FREEZE ... between data updates, which will give you the best performance possible= .=20=20 But not if the data is actually going to be edited, even slightly. See the online manual entries about VACUUM for an explanation. --=20 -Josh Berkus Aglio Database Solutions San Francisco