I've come across a few situations where I've needed to drop some check 
constraints on the subscribers to allow the initial data subscription to 
happen.  In thinking about this I have come up with the following proposal 
which I'd like some feedback on prior to implementing.

I propose, that rather than hacking around the system catalogs and manually 
setting things like tg_enable=false.  That we probe each table during the set 
table add command checking for CHECK/RULE/TRIGGERS, get the textual creation 
syntax of these objects  (the same as pg_dump does), store these within a 
coresponding table in the cluster schema, then issue an ALTER TABLE ... DROP 
TRIGGER/CONSTRAINT/RULE.  These objects are then restored at the appropriate 
time when the cluster is uninstalled, or failed-over.

Does anybody have any concerns with doing things this way as opposed to our 
existing method?


-- 
Darcy Buskermolen
Wavefire Technologies Corp.
ph: 250.717.0200
fx:  250.763.1759
http://www.wavefire.com