Received: from megazone.bigpanda.com ([63.150.15.178]) by postgresql.org (8.11.3/8.11.4) with ESMTP id fAKHvwm35194 for ; Tue, 20 Nov 2001 12:57:58 -0500 (EST) (envelope-from sszabo@megazone23.bigpanda.com) Received: by megazone.bigpanda.com (Postfix, from userid 1001) id 21C81D5E6; Tue, 20 Nov 2001 09:58:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by megazone.bigpanda.com (Postfix) with ESMTP id 1573C5BE7; Tue, 20 Nov 2001 09:58:04 -0800 (PST) Date: Tue, 20 Nov 2001 09:58:04 -0800 (PST) From: Stephan Szabo To: Cc: Subject: Re: SELECT * FROM t where p or q; In-Reply-To: <3BFA95ED.EE814258@efbs-seafrigo.fr> Message-ID: <20011120095544.L57636-100000@megazone23.bigpanda.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200111/297 X-Sequence-Number: 5679 On Tue, 20 Nov 2001 frbn@efbs-seafrigo.fr wrote: > thanks to you, after a 15mn long "vacuum ANALYZE table" :( Ugh. 7.2s vacuum will be much happier (since it doesn't lock the tables from other usual use - yay Tom!) but I think there's also some things you may be able to do to speed it up. It's possible dropping indexes and recreating them may be faster. > I can't figure out how Tera-bytes databases admins can > deal with such vacuum delays! > (except if a vacuum is only needed every 10 millions records :] ) It mostly depends on the frequency of deletes and updates to the database.