pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Rural Hunter <ruralhunter@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Large historical tables and autovacuum
Date: Tue, 11 Sep 2012 09:57:22 +0800
Message-ID: <504E9A82.6070504@gmail.com> (raw)
In-Reply-To: <CAAo2Tf9O8LMKR_VRT0eGtdvHtSBugZQuWAu8sekFH0SMntcVbg@mail.gmail.com>
References: <CAAo2Tf9O8LMKR_VRT0eGtdvHtSBugZQuWAu8sekFH0SMntcVbg@mail.gmail.com>

turn auto vacuum off for those tables.

于 2012/9/11 4:30, David Morton 写道:
> We have many large tables which contain static historical data, they 
> are auto vacuumed on a regular basis (sometimes to prevent wraparound) 
> which i suspect causes a few annoying side effects:
> - Additional WAL file generation
> - Increased 'changed' data as far as our online rsync based backups 
> are concerned
>
> Is there any way to tell Postgres that these tables are now not 
> available for changes so we can avoid these seemingly pointless 
> maintenance tasks ?
>
> Dave

view thread (6+ messages)  latest in thread

Message-ID: <504E9A82.6070504@gmail.com>
Permalink:  ../504E9A82.6070504@gmail.com/
Also on:    postgresql.org/message-id/504E9A82.6070504@gmail.com

copy link · copy postgr.es

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-admin@postgresql.org
  Cc: ruralhunter@gmail.com
  Subject: Re: Large historical tables and autovacuum
  In-Reply-To: <504E9A82.6070504@gmail.com>

* 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