Re: Call closed: Almost happy ending (from "Data files became huge with no apparent reason" thread) - Mailing list pgsql-general

From Martijn van Oosterhout
Subject Re: Call closed: Almost happy ending (from "Data files became huge with no apparent reason" thread)
Date
Msg-id 20020904115506.B22333@svana.org
Whole thread Raw
In response to Re: Call closed: Almost happy ending (from "Data files became huge with no apparent reason" thread)  (Dario Fumagalli <dfumagalli@tin.it>)
Responses Re: Call closed: Almost happy ending (from "Data files became huge with no apparent reason" thread)  (Alvaro Herrera <alvherre@atentus.com>)
Re: Call closed: Almost happy ending (from "Data files became huge with no apparent reason" thread)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Sep 03, 2002 at 05:40:25PM +0200, Dario Fumagalli wrote:
> As I stated in an earlier post, i vacuumed was about 2 - 3 weeks earlier
> (my vacation duration).

Seriously, setup a vacuum to run daily. The time wasted by scanning overly
large tables and using inexact statistics far exceeds a once-per-day delay
caused by a vacuum.

> Yes, in this database insert / upate ratio is 1 : 180, and db updates
> are performed 4 times a day by an external PHP console script.

Well, do a vacuum after each update for maximum performance.

I actually had a thought last night. REINDEX recreates the index, probably
with *all* rows in the table, whether or not they are still active. Thus, to
get maximum effect from REINDEX, you need to VACUUM first.

Maybe someone with more knowledge than me can confirm this.
--
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> There are 10 kinds of people in the world, those that can do binary
> arithmetic and those that can't.

pgsql-general by date:

Previous
From: Martijn van Oosterhout
Date:
Subject: Re: Columns in views
Next
From: "Linn Kubler"
Date:
Subject: Re: parameterized views?