Re: Large historical tables and autovacuum

From: Fernando Hevia <fhevia(at)gmail(dot)com>
To: David Morton <davidmorton78(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Large historical tables and autovacuum
Date: 2012-09-11 03:57:14
Message-ID: CAGYT1XSoKkiD53SgynUZJtXwiBoWMYLWqdpVYvZoTf83DZ7aOw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Mon, Sep 10, 2012 at 5:30 PM, David Morton <davidmorton78(at)gmail(dot)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
);

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David Morton 2012-09-11 04:04:22 Re: Large historical tables and autovacuum
Previous Message Rural Hunter 2012-09-11 01:57:22 Re: Large historical tables and autovacuum