Mark Hagger <mark.hagger at mxdata.co.uk> writes:
> Just to clarify, your plan would mean that I would be able to:<BR>
> <BR>
> 1) run a script that dumps enough information to re-create the cluster from its current state<BR>
> 2) do the various unsubscribes/uninstalls of slony 1.x bits<BR>
> 3) Install new slony 2.x code<BR>
> 4) run this dumped script (more or less) to bring my cluster back to life<BR>
> <BR>
> For me the key bit is (1), since my cluster configurations (I have several created over a long period of time) means that my heart sinks at the idea of<BR>
> having to re-create all the clusters from scratch, plus the OMIT COPY bit looks like a huge win.<BR>
> <BR>

That sounds about right!

Here's the script to "dump enough information"...

<http://main.slony.info/viewcvs/viewvc.cgi/slony1-engine/tools/slonikconfdump.sh?revision=1.1.2.4&view=markup&sortby=date>

You should be able to run that script against your existing cluster;
I'd urge that you try it out, to see what output you get, and to
validate that it agrees with what you'd expect.
-- 
let name="cbbrowne" and tld="ca.afilias.info" in name ^ "@" ^ tld;;
<http://dba2.int.libertyrms.com/>
Christopher Browne
(416) 673-4124 (land)
"Bother,"  said Pooh,  "Eeyore, ready  two photon  torpedoes  and lock
phasers on the Heffalump, Piglet, meet me in transporter room three"