On Mon, Sep 20, 2010 at 12:26 PM, Brad Nicholson
<bnichols at ca.afilias.info> wrote:
>  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.

Thank you.   I see how to control autovacuuming using ALTER TABLE.
So Vick and Brad both let Postgres autovacuum the Slony tables.

I propose a patch to http://www.slony.info/documentation/maintenance.html :

Change section title from
"6.1. Interaction with PostgreSQL autovacuum"
to
"6.1. Interaction with PostgreSQL 8.1 and 8.2 autovacuum"

Change
"The following query (change the cluster name to match your local
configuration) will identify the tables that autovacuum should be
configured not to process"
to
"The following query (change the cluster name to match your local
configuration) on Postgres 8 versions up to and not including 8.4 will
identify the tables that autovacuum should be configured not to
process"

Change
"The following query will populate pg_catalog.pg_autovacuum with
suitable configuration information:  "
to
"The following query (for Postgres versions up to and not including
8.4) will populate pg_catalog.pg_autovacuum with suitable
configuration information:  "

Best,
-at