On Mon, Apr 07, 2008 at 09:44:22AM +1000, James Tucker wrote:
> 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 .

Among other things, yes.  The short answer is Don't Do That.  The other
poster suggested what you can do.

The other approach is to use the "bare metal" functions.  These are
documented in the Slony manual.

A