Hello!

I'm evaluating Slony as a solution for the system we're building.

I'd like to run what i'm planning to do by the group to see if what
I want to do is even possible. 

I've got two servers / databases. NodeA and NodeB

NodeA replicates to NodeB.

for my nightly processing, I have some jobs that will update a large number 
of records, and would basically result in the system unavailable (could be 
a few hours).

What I'd like to do, is to run those Jobs in NodeB and then at the end
of the process "swap" NodeB and NodeA.

>From what i've read of slony so far, I think i can do at least that much.


So the concern is - up until the "swap" I need to be able to access and even 
update records in NodeA and I want to continue replicating between NodeA and 
NodeB.

During that time, I can control the records that are inserted/updated in
NodeA so I know that they wouldn't impact anything that is currently
running into NodeB.

Is that possible? (is there a better/ or standard way that I'm missing?)

Thanks

Dave