Gordon Shannon <gordo169 at gmail.com> writes:
> Christopher Browne wrote:
>> 
>> Happily, when I "forked" the function into 8.3 and 8.4 versions, it
>> turns out that the API was perfectly fine for either; indeed, the
>> change to pull data from pg_class rather than pg_autovacuum is
>> relatively minor within the function.
>> 
>> I just committed that to 2.0+HEAD.
>> 
>
> Cool.  My hope is that, since the slony package creates the slony
> tables, that you will create them with no special autovacuum
> settings. That way, if I have autovacuum turned on in my system,
> then autovacuum will vacuum all Slony tables, rather than Slony
> doing it.  I just want to be sure that Slony doesn't ever vacuum
> sl_log_1 or sl_log_2, since it's a waste of time as they are
> truncated.  Please let me know if my assumptions is wrong.

Exactly so, at least as the default setting.

There are 3 distinguishable behaviours:

- By default, with 8.3/8.4, autovac is running, and the Slony-I tables
  will be caught by autovac, with the result that the Slony-I cleanup
  thread won't bother vacuuming them.

- If *you* set sl_log_1/sl_log_2 to be excluded by autovac, then the
  Slony-I cleanup process will vacuum them.

- On the other hand, if you shut off autovac, then the Slony-I cleanup
  process will notice, and vacuum *all* of its tables.

You can choose any of the three options...
-- 
select 'cbbrowne' || '@' || 'ca.afilias.info';
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"