On Thu, Oct 06, 2005 at 11:20:33AM -0700, Alan Hodgson wrote:
> On Thu, Oct 06, 2005 at 02:01:00PM -0400, Tim Goodaire wrote:
> > > You might need to target such ddl changes to all nodes in a replication 
> > > topology (your enterprise wide schema), but like your data replicated 
> > > individually between nodes. That's the case I'm talking about.
> > 
> > Ok. It's becoming a little more clear for me. I think. 
> > 
> > You would like to be able to apply ddl changes to all sets in a cluster.
> 
> Which of course you can't do, because Slony will only restore the triggers for
> tables in the particular set that the DDL change is propogating through, not
> tables in other sets.  If your DDL change touches one of those other tables,
> either making direct trigger changes or even referenced as foreign keys, it
> it fail badly.

Right. This would of course become even more complicated if you have a bunch
of sets, each with a different origin, plus foreign keys.

Tim


> 
> -- 
> "A government that robs Peter to pay Paul can always depend upon the support 
> of Paul." - George Bernard Shaw
> 
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at gborg.postgresql.org
> http://gborg.postgresql.org/mailman/listinfo/slony1-general

-- 
Tim Goodaire    416-673-4126    tgoodair at ca.afilias.info
Database Administrator, Afilias Canada Corp.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://gborg.postgresql.org/pipermail/slony1-general/attachments/20051006/d3c01229/attachment-0001.bin