Re: Shortening time of vacuum analyze - Mailing list pgsql-general

From Francisco Reyes
Subject Re: Shortening time of vacuum analyze
Date
Msg-id 20020130170348.H41256-100000@zoraida.natserv.net
Whole thread Raw
In response to Re: Shortening time of vacuum analyze  (Andrew Sullivan <andrew@libertyrms.info>)
List pgsql-general


On Wed, 30 Jan 2002, Andrew Sullivan wrote:

> On Wed, Jan 30, 2002 at 12:23:50PM -0500, Francisco Reyes wrote:
>
> > You can put the delete/load inside a transaction so the users will never
> > see an empty table. Truncate can not be placed inside a transaction.
>
> True enough.  But why not leave the table unvacuumed, then, until a
> more convenient time?  You are, of course, paying a cost in
> performance during that time, but not as great as you would with
> vacuum.

We do the vacuum right after the load of all the new tables, but before we
do all our daily reports. An operation that takes 30 minutes if all is
vacuumed takes about 2 hours if not vacuumed.

Given that 7.2 is due out shortly I have comed up with some other ways of
improving time.. ie delaying re-freshing some data which rarely ever
changes until 7.2 is out.


pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: process exited with status 11 after XLogFlush: request is not satisfied
Next
From: Marc Munro
Date:
Subject: Row-based security (virtual private database)