Re: Large historical tables and autovacuum

What are the implications of doing this ?
Some times we experience the vacuum being started to prevent wraparound, i
understand this will always take place if required regardless of autovacuum
settings ?

Is there any way of making the table 'read only' so its nice and tidy
/ immutable ?

Dave

On Tue, Sep 11, 2012 at 3:57 PM, Fernando Hevia <fhevia(at)gmail(dot)com> wrote:

>
> 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
> );
>