> 375000 log rows and no subscriber more than 40 seconds behind ... that 
> looks like someone was doing mass updates here.

Or perhaps a long running transaction doing other things (pg_dump,
client idle in transaction, etc) in the background which causes a
similar backlog for the slony cleaning mechanisms.

--