Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f26FVsx16182 for ; Tue, 6 Mar 2001 10:31:54 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f26FVn905529; Tue, 6 Mar 2001 10:31:49 -0500 (EST) To: Justin Long cc: pgsql-sql@postgresql.org Subject: Re: Optimizing Query In-reply-to: <5.0.2.1.0.20010306091755.03723ea0@mail.strategicnetwork.org> References: <5.0.2.1.0.20010305165854.03114e48@mail.strategicnetwork.org> <20010305224029.A22983@ilse.nl> <5.0.2.1.0.20010305165854.03114e48@mail.strategicnetwork.org> <5.0.2.1.0.20010306091755.03723ea0@mail.strategicnetwork.org> Comments: In-reply-to Justin Long message dated "Tue, 06 Mar 2001 09:18:41 -0500" Date: Tue, 06 Mar 2001 10:31:48 -0500 Message-ID: <5525.983892708@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/100 X-Sequence-Number: 1750 Justin Long writes: > Wow. I can't believe the difference. It didn't take too long. I'll set up a > script in my etc/cron.weekly to run it... would there be any benefit to > doing a vacuum analyze nightly? Depends. A nightly vacuum is probably good practice, but you could skip the analyze part if your data statistics (such as column min and max values) don't change much. regards, tom lane