Date: Wed, 25 Apr 2007 23:07:16 -0400
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Aaron Bono <postgresql@aranya.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Richard Huxton <dev@archonet.com>,
	PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Re: Query Join Performance
Message-ID: <20070426030716.GD10666@alvh.no-ip.org>
Mail-Followup-To: Aaron Bono <postgresql@aranya.com>,
	Tom Lane <tgl@sss.pgh.pa.us>, Richard Huxton <dev@archonet.com>,
	PostgreSQL SQL List <pgsql-sql@postgresql.org>
References: <bf05e51c0704241826u3e6652d1m26973b837e0b1397@mail.gmail.com>
	<462F9714.8090802@archonet.com>
	<bf05e51c0704251339u2883211eh4cdedcbec63c2be9@mail.gmail.com>
	<6573.1177539802@sss.pgh.pa.us>
	<bf05e51c0704251757o311dd849n2c6a52e1c68b933e@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <bf05e51c0704251757o311dd849n2c6a52e1c68b933e@mail.gmail.com>
User-Agent: Mutt/1.5.13 (2006-08-11)

Aaron Bono wrote:

> Looks like a vacuum analyze did the trick.  Performance is beautiful now.  I
> should have tried that earlier.
> 
> I thought I had the auto vacuum turned on (PostgreSQL 8.1) but I guess it
> doesn't do analyze?
> 
> Anyway, I will schedule a vacuum analyze nightly - it is low usage and won't
> cause any problems.

It should have done an analyze at some point.  Unless this is Windows,
in which case there's a bug that precludes autovacuum from running at
all.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.