Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
Cc: Satoshi Nagayasu <nagayasus(at)nttdata(dot)co(dot)jp>, pgsql-patches(at)postgresql(dot)org
Subject: Re: enable/disable trigger (Re: Fwd: [HACKERS] Open items)
Date: 2005-07-01 13:43:42
Message-ID: 28395.1120225422@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> writes:
> The table owner can drop and create triggers - so why shouldn't they be
> able to enable and disable them?

Not triggers belonging to RI constraints on other tables.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-07-01 13:53:36 Re: [PATCHES] Users/Groups -> Roles
Previous Message Tom Lane 2005-07-01 13:19:30 Re: Occupied port warning

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2005-07-01 13:53:36 Re: [PATCHES] Users/Groups -> Roles
Previous Message Stephen Frost 2005-07-01 12:49:52 Re: [PATCHES] Users/Groups -> Roles