Re: Disable and enable of table and column constraints

Поиск
Список
Период
Сортировка
Искать
От
Kevin Grittner
Тема
Re: Disable and enable of table and column constraints
Дата
Msg-id
4AAE0D2A020000250002AECC@gw.wicourts.gov
Ответ на
Список
Дерево обсуждения
Re: Disable and enable of table and column constraints Christopher Browne <cbbrowne@ca.afilias.info>
Re: Disable and enable of table and column constraints Tom Lane <tgl@sss.pgh.pa.us>
Re: Disable and enable of table and column constraints Jan Wieck <JanWieck@Yahoo.com>
Re: Disable and enable of table and column constraints Martijn van Oosterhout <kleptog@svana.org>
Re: Disable and enable of table and column constraints "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
>Martijn van Oosterhout  wrote:
> 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.
Yeah, as a general rule it doesn't make sense to try to enforce
constraints on a replication *target*.  Check and report, perhaps, but
you don't normally want to error out on anything which you know was
actually applied to the source database.  It's even worse for some
classes of triggers which generate derived data; you don't want the
replication to generate one value and then a trigger on the
replication target to try to do the same.  A count, for example, could
easily wind up with an "off by one" error much of the time.
-Kevin

В списке pgsql-hackers по дате отправления
От: Pierre Frédéric Caillaud
Дата:
Сообщение: Bulk Inserts
От: Jeff Janes
Дата:
FAQ