Mon Sep 20 12:26:33 PDT 2010
- Previous message: [Slony1-general] How to disable PostgreSQL autovacuum of Slony tables? (getting error: column "_" does not exist)
- Next message: [Slony1-general] How to disable PostgreSQL autovacuum of Slony tables? (getting error: column "_" does not exist)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10-09-17 08:25 AM, Vick Khera wrote: > On Thu, Sep 16, 2010 at 8:19 PM, Aleksey Tsalolikhin > <atsaloli.tech at gmail.com> wrote: >> The Slony maintenace docs recommend disabling PostgreSQL autovacuum >> on the Slony tables (http://www.slony.info/documentation/maintenance.html) >> but the command to identify the tables fails: >> > I'm running an 8.3 cluster and I have not disabled autovacuum on the > slony tables. I have not had any problems. I think modern autovacuum > is smart enough to work this way. I also run a manual vacuum on my > whole DB every night. > Same here. We have also disabled the slon triggered vacuums and let autovacuum handle everything. To answer the OP question about pg_autovacuum - yes, the table has gone away in Postgres 8.4. Autovacuum settings on a per-table basis are controlled in with the tables storage parameters now via CREATE/ALTER table. http://www.postgresql.org/docs/9.0/interactive/sql-createtable.html#SQL-CREATETABLE-STORAGE-PARAMETERS Perhaps the docs should be updated to reflect this. -- Brad Nicholson 416-673-4106 Database Administrator, Afilias Canada Corp.
- Previous message: [Slony1-general] How to disable PostgreSQL autovacuum of Slony tables? (getting error: column "_" does not exist)
- Next message: [Slony1-general] How to disable PostgreSQL autovacuum of Slony tables? (getting error: column "_" does not exist)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list