From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Christopher Browne <cbbrowne(at)ca(dot)afilias(dot)info>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Disable and enable of table and column constraints |
Date: | 2009-09-12 12:06:34 |
Message-ID: | 20090912120634.GA5285@svana.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Sep 10, 2009 at 04:24:15PM -0400, Jan Wieck wrote:
> The feature was originally intended to be a clean way of avoiding
> interferences of triggers and/or foreign keys with replication systems
> that work on the user level (like Bucardo, Londiste and Slony). The only
> way to break foreign keys in that scenario is to replicate a referencing
> table without replicating the corresponding PK table.
FWIW, I find the ability in Slony to configure triggers so they work or
not depending on the replication role to be extremely useful. Absolutely
a major positive feature.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2009-09-12 15:13:39 | Re: COPY enhancements |
Previous Message | Grzegorz Jaskiewicz | 2009-09-12 12:06:17 | Re: clang's static checker report. |