>
>
>> 3. Drop _myrep schema which copied by pg_dump to slave ( Note: This is
>> not documented, I suspect when we copy masterdb schema structure u also
>> get the _slonyschema as well. Which throw error as _slonyschema
>> existing. Do we really need master _slonyschema to new node ?)
>>
>
> No you do not need to dump the slonyschema, you can exclude that from your
> dump.
>
> Yes, I did the step 1 under section 3.2.4. Because, add replication node
will be on the existing replication, so the dump mentioned in the
documentation will include the slony schema. Need to changed in
documentation.

http://slony.info/documentation/2.1/modifyingthings.html

 output of the subscribe node;
>> -bash-4.1$ ./new_node_subscribe-set.sh
>> waiting for events  (3,5000000001) only at (3,0) to be confirmed on node 1
>> waiting for events  (3,5000000001) only at (3,0) to be confirmed on node 1
>> waiting for events  (3,5000000001) only at (3,0) to be confirmed on node 1
>>
>> I found the link which pointing to some bug. Correct me, how to achive
>> this.
>>
>
> Did you start the slon daemon for the new node?  If not, starting the slon
> daemon for the new node should allow things to replicate
>

Small things, create big problems .. :). Yes after starting Slave slon
daemon, everything goes well.

--Raghav
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.slony.info/pipermail/slony1-general/attachments/20120619/2c3dcb38/attachment.htm