Re: Change the default [tgenabled] for new "internal" triggers ?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: david(dot)sahagian(at)emc(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Change the default [tgenabled] for new "internal" triggers ?
Date: 2012-03-26 15:03:07
Message-ID: 25512.1332774187@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

<david(dot)sahagian(at)emc(dot)com> writes:
> But my email was about the "internally generated constraint triggers"
> which implement checking for Foreign Key Constraint violations.

Yeah ...

> It is that checking that I want to be done on the Secondary.
> Should I not want such checking to be done ?

What for, when it was already checked on the master? Perhaps more to
the point, FK triggers can make updates not only checks.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Rainer Pruy 2012-03-26 15:16:14 Re: can these queries be combined into one?
Previous Message david.sahagian 2012-03-26 14:55:21 Re: Change the default [tgenabled] for new "internal" triggers ?