Re: Disabling triggers / constraints

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, kell_pt(at)users(dot)sourceforge(dot)net, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Disabling triggers / constraints
Date: 2004-05-21 05:11:51
Message-ID: 23625.1085116311@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> It should be a per-table thing:

Exactly. I don't care whether you're superuser, you should not be able
to disable all triggers, and certainly any facility provided for this
purpose should not encourage you to do that instead of disabling just
the triggers you need. Think about the triggers on pg_shadow ...

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Hammond 2004-05-21 13:34:04 Re: pg_ctl patch to integrate apache's rotatelogs
Previous Message Christopher Kings-Lynne 2004-05-21 05:09:53 Re: Disabling triggers / constraints