> On 10/12/2004 10:35 AM, hannu at skype.net wrote:
>
>> Ok Now I was at leas able to convince slony to drop node5 , but I still
>> have
>> sl_log_1 file of 3.3M rows.
>>
>> This manifests itself as periods of tens of seconds when the system
>> halts
>> to a crawl as slony vacuums that big table and clients timeout. The
>> selects form sl_log_1 are slow as well, but at least they do not affect
>> other operations ;(
>>
>> My current solution is to stop slony on slaves during peak periods, but
>> what I really would like is that the sl_log_1 could be trimmed down.
>
> We have to work on log switching ... yes.

Currently I would be happy if I got some advice how to do it manually

Where can I find out what slon is waiting for and which entries are safe
to delete.

I assume that it must be waiting for something that will never happen as
currently I runit with only one master and one slave and replica being
up-to-date.

-------------
Hannu