Run an EXECUTE SCRIPT on the cluster?
The good part here is that you can run it node by node to help locking
contention.

Andreas

Am Montag, den 07.04.2008, 09:44 +1000 schrieb James Tucker:
> Hi All,
> 
> We have recently experienced an incident whereby certain tables were
> directly updated and new columns and constraints added without using
> the execute script function.  We are now receiving errors (ERROR:
> Slony-I: old key column TTT.FFF IS NULL on {UPDATE,DELETE}) on certain
> transactions, and these transactions are being rolled back.  The DDL
> changes were also done on the slave node, so schemas are are both
> correct.  I believe the issue is to do with the triggers not being
> updated after .
> 
> What is the best way to update/rebuild the existing triggers on tables
> which have been modified ? 
> 
> Thanks
> 
> James
> _______________________________________________
> Slony1-general mailing list
> Slony1-general at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-general
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
Url : http://lists.slony.info/pipermail/slony1-general/attachments/20080407/8ece17d7/attachment.pgp