Hi,

A client has an installation of slony I 1.2.15 with pg 8.3.7 and they
are having troubles with the size of the database...
while checking i found that sl_log_2 has more than  102784620 dead
tuples and the table size grows to 22gb, vac_frecuency is 0 and
autovacuum is enabled but no vacuum has happened... i will execute a
manual vacuum later today when the impact is not so big

AFAIUI, slony should switch sl_log_* tables from time to time and then
truncate the other one but i don't see sl_log_1 being used (never), it
has 0 live tuples and 0 dead tuples...

ideas?

-- 
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157