Aha, does uninstallnode() clean up anything that drop cascade will not?

----- Original Message ----
> From: Stéphane A. Schildknecht <stephane.schildknecht at postgresqlfr.org>
> To: Glyn Astill <glynastill at yahoo.co.uk>
> Cc: slony1-general at lists.slony.info
> Sent: Tuesday, 13 May, 2008 1:50:43 PM
> Subject: Re: [Slony1-general] Stripping out slony after / before / during pg_restore?
> 
> Glyn Astill a écrit :
> > Hi people,
> > 
> > I'm setting us up a separate staging / test server and I want to read in a 
> pg_dump of our current origin stripping out all the slony stuff.
> > 
> > I was thinking this could serve two purposes a) test out backups restore 
> properly and b) provide us with us with the staging / test server
> > 
> > What's the best way to remove all the slony bits?
> > 
> > I was thinking read in the dump, then use uninstall node - but I'd rather not 
> have to run the slon daemons.
> 
> You don't have to run any slon daemon to execute uninstallnode().
> 
> You just have to execute something like "select _YOURINSTANCE.uninstallnode()"
> on the newly restored DB.
> 
> You can the drop the entire schema (drop schema _YOURINSTANCE cascade).
> 
> > 
> > Or should I just leave all the slony stuff in there... would it cause us any 
> problems? There'd be no slons running and the next night it's all wiped and 
> restored again...
> 
> Not sure leaving all slony stuf is really a good option as it does :
> - modify the catalog schema
> - log every modification in data as slony triggers will stay up and active.
> 
> > 
> > Anyone got any ideas? Anyone got something similar already?
> 
> I do restore the whole master db and uninstall/drop every slony stuff.
> 
> Best regards,
> -- 
> Stéphane SCHILDKNECHT
> Président de PostgreSQLFr
> Tél. 09 53 69 97 12
> http://www.postgresql.fr



      __________________________________________________________
Sent from Yahoo! Mail.
A Smarter Email http://uk.docs.yahoo.com/nowyoucan.html