Bill Moran <wmoran at collaborativefusion.com> writes:
> In response to "Diego Algorta Casamayou" <diego.algorta at gmail.com>:
>
>> On Jan 22, 2008 11:16 AM, Raymond O'Donnell <rod at iol.ie> wrote:
>> > On 22/01/2008 13:11, Diego Algorta Casamayou wrote:
>> >
>> > > What usage could I give to this restored database? May I use it as a
>> > > master in case the master died? In that case I think a failover to the
>> > > running slave would be faster.
>> >
>> > Well, it's a backup - no more and no less. The whole point of Slony (or
>> > any replication system) is that you have a nearly-up-to-date copy of
>> > your database to which you can failover if the master goes belly-up. A
>> > backup is always going to be less current than a well-running Slony slave.
>> 
>> I know, I know. But for example, I currently have full backups made
>> from my master node. And restoring that backup to use it as an
>> independent database doesn't really work because it still has slony
>> all over the place. Running UNINSTALL NODE on it doesn't work either.
>> 
>> >
>> > > What should I do to use it in a non-replicated environment? A staging
>> > > environment, for example for testing purposes where I need
>> > > production-like data.
>> >
>> > That's what I do; as well as keeping a copy as a backup, of course. :-)
>> 
>> OK. But what do you do to get rid of slony on that restored database?
>
> DROP SCHEMA _[clustername] CASCADE;
> ... always works for me.
>
>> This should be a common issue, but I can't find a clear note on it on
>> the documentation.
>
> Don't know why that's not documented.  Anyone?

In the "fabled next version," that does indeed become the full method,
in that ALL of the objects that Slony-I creates will be enclosed in
that schema.

In v1.0-v1.2, there is regrettably more to it.

 - Any tables defined using TABLE ADD KEY (to put in a surrogate primary key)
   need to have the extra column dropped

 - On subscribers, rules and triggers need to get "relinked" because
   the catalog gets hacked up to deactivate them.

So on 1.0-1.2, the "right answer" is to use the slonik command
"UNINSTALL NODE," which seems reasonably documented...
-- 
let name="cbbrowne" and tld="cbbrowne.com" in String.concat "@" [name;tld];;
http://cbbrowne.com/info/advocacy.html
Roses are red
Violets are blue
Some poems rhyme
But this one doesn't.