Only way to stop Postgres chewing all the CPU


------Original Message------
From: Jan Wieck
To: Tim Lloyd
Cc: slony1-general at lists.slony.info
Subject: Re: [Slony1-general]  Slony replication problem - logswitch failure
Sent: Mar 26, 2011 22:53

On 3/26/2011 6:43 AM, Tim Lloyd wrote:
> Hi Venkat
>
> I found a way to get Slony out of this state without rebuilding the db.
>
> 1) Connect to your database, e.g. psql<dbname>  as user postgres
>
> 2) delete from _schema.sl_log_1;

Looks a little bit dangerous to me. YMMV.


Jan

-- 
Anyone who trades liberty for security deserves neither
liberty nor security. -- Benjamin Franklin


Sent from my BlackBerry® wireless device