Re: Large historical tables and autovacuum - Mailing list pgsql-admin

From Fernando Hevia
Subject Re: Large historical tables and autovacuum
Date
Msg-id CAGYT1XSoKkiD53SgynUZJtXwiBoWMYLWqdpVYvZoTf83DZ7aOw@mail.gmail.com
Whole thread Raw
In response to Large historical tables and autovacuum  (David Morton <davidmorton78@gmail.com>)
Responses Re: Large historical tables and autovacuum  (David Morton <davidmorton78@gmail.com>)
List pgsql-admin

On Mon, Sep 10, 2012 at 5:30 PM, David Morton <davidmorton78@gmail.com> wrote:
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 ?

ALTER TABLE table_name SET (
  autovacuum_enabled = false
); 

pgsql-admin by date:

Previous
From: Rural Hunter
Date:
Subject: Re: Large historical tables and autovacuum
Next
From: David Morton
Date:
Subject: Re: Large historical tables and autovacuum