You may also want to merge set 3 back to the set you wanted
it in in the first place.

--elein
elein at varlena.com

On Fri, Jan 13, 2006 at 04:00:55PM -0500, Sven Willenberger wrote:
> On Fri, 2006-01-13 at 12:31 -0800, Alan Hodgson wrote:
> > On January 13, 2006 12:25 pm, Sven Willenberger <sven at dmv.com> wrote:
> > > So my question is whether there is any way to add tableB such that it
> > > now replicates from server2 to server1? Or is it possible to change the
> > > subcription definition of server3 to set FORWARD = yes and could I then
> > > set up replication from server3 to server1 as follows:
> > >
> > > server3 [origin] --> Set 3 [tableB] --> server1
> > >
> > > Or will I still fail due to the table_reloid constraint?
> > 
> > You need to move the table to a third set that is replicated to the 
> > necessary servers.
> > 
> 
> I came to the same conclusion about 5 minutes after I sent the email. I
> ended up dropping replication of the table and sequence, created a new
> set that had the one server as origin and the other 2 as subscribers,
> added the table and sequence to this new set and started subscribed the
> nodes. All worked well :-)
> 
> Thanks,
> 
> Sven
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general
>