pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthew T. O'Connor <matthew@zeut.net>
To: Csaba Nagy <nagy@ecircle-ag.com>
Cc: Edoardo Ceccarelli <eddy@axa.it>
Cc: postgres performance list <pgsql-performance@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
Date: Wed, 27 Sep 2006 14:33:10 -0400
Message-ID: <451AC3E6.5050108@zeut.net> (raw)
In-Reply-To: <1159373624.3874.187.camel@coppola.muc.ecircle.de>
References: <451AA1FE.9050704@axa.it>
	<1159373624.3874.187.camel@coppola.muc.ecircle.de>

Csaba Nagy wrote:
> On Wed, 2006-09-27 at 18:08, Edoardo Ceccarelli wrote:
>   
>> How can I configure the vacuum to run after the daily batch insert/update?
>>     
>
> Check out this:
> http://www.postgresql.org/docs/8.1/static/catalog-pg-autovacuum.html
>
> By inserting the right row you can disable autovacuum to vacuum your big
> tables, and then you can schedule vacuum nightly for those just as
> before. There's still a benefit in that you don't need to care about
> vacuuming the rest of the tables, which will be done just in time.

In addition autovacuum respects the work of manual or cron based 
vacuums, so if you issue a vacuum right after a daily batch insert / 
update, autovacuum won't repeat the work of that manual vacuum.





view thread (17+ messages)  latest in thread

Message-ID: <451AC3E6.5050108@zeut.net>
Permalink:  ../451AC3E6.5050108@zeut.net/
Also on:    postgresql.org/message-id/451AC3E6.5050108@zeut.net

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: matthew@zeut.net, nagy@ecircle-ag.com, eddy@axa.it, pgsql-admin@postgresql.org
  Subject: Re: [PERFORM] autovacuum on a -mostly- r/o table
  In-Reply-To: <451AC3E6.5050108@zeut.net>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox