On 6/24/2004 8:53 AM, Thomas Draband (madcow) wrote:
> Thomas Draband (madcow) schrieb:
>> After an immediate stop of postgresql (simulation of system crash) in 
>> pg_catalog.pg_listener a tupel with relname='_${cluster_name}_Restart' 
>> exists. slon doesn't start cause it thinks another process is serving 
>> the cluster on this node.
>> What can I do? The tupels can't be droped from this relation.
>> 
>> _______________________________________________
>> Slony1-general mailing list
>> Slony1-general at gborg.postgresql.org
>> http://gborg.postgresql.org/mailman/listinfo/slony1-general
> 
> I've found an anwser my self.
> Befor I start slon, I do a 'restart node'. PostgreSQL tries to nothify 
> the listeners and drop those are not anwsering. Slon then starts cleanly.

That's a cool solution ... I was thinking about trying to detect things 
in slon, but didn't see the easy way.

This should be added to the appropriate documentation, please.


Jan

> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck at Yahoo.com #