Hi all,

On Wed, 2009-10-07 at 03:43 +0200, Vick Khera wrote:
> I'm of the opinion that if the implicit trigger still fires on the
> replica it is not a horrible thing.  It just wastes some cycles.  In
> my case ultimately the new table was to be added to replication.  I
> just wanted to avoid the burden of shutting down things enough that an
> EXECUTE SCRIPT could successfully run.  The rate of change on this DB
> is very high and I usually end up with some failure unless I disable
> sections of the app.

Wouldn't it work to run the table creation via EXECUTE SCRIPT only on
the slaves ? I think it is possible to run EXECUTE SCRIPT only on a
selected node, so you would run it directly on the master, and
separately via EXECUTE SCRIPT on the slave(s). I guess a short full
downtime on a slave is acceptable, except of course if you also use the
slaves for select... then maybe it would work to create the table on the
slaves by taking them off-line one by one.

Cheers,
Csaba.