-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Darcy Buskermolen wrote:
| 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?

That has caused a "certain amount of grief" around here, so I'd be
agreeable in at least general terms to this.

This approach has the further merit that doing a pg_dump on a subscriber
node gets results that aren't "hacked up."
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBdERRCVn6LJfHIAIRArk8AKCTmDKZ/LvKCYgkbDOq7vvjoZFUVACfdQ3P
AdYTv7yU63+EWAbRFG+YPHA=
=0xsG
-----END PGP SIGNATURE-----