Re: Inheritance of foregn key constraints - dropping isinternal triggers by a

From: Andrzej Mazurkiewicz <andrzej(at)mazurkiewicz(dot)org>
To: fabriziomello(at)gmail(dot)com
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Inheritance of foregn key constraints - dropping isinternal triggers by a
Date: 2014-04-02 14:45:30
Message-ID: 2729604.PO7CB1FP43@tata
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tuesday 01 of April 2014 11:06:00 you wrote:
> On Tue, Apr 1, 2014 at 9:13 AM, Andrzej Mazurkiewicz <
>
> andrzej(at)mazurkiewicz(dot)org> wrote:
> > It seems that if the trigger is internal (tgisinternal = true) it is not
> > visible to the DROP TRIGGER command. So it cannot be deleted using DROP
> > TRIGGER command, although the dependency type is DEPENDENCY_AUTOMATIC
>
> Try using a quoted identifier:
>
> DROP TRIGGER "RI_ConstraintTrigger_c_19322" ON master;
>
> Regards,
>
> --
> Fabrízio de Royes Mello
> Consultoria/Coaching PostgreSQL
Good Afternoon.

Sorry for my mistake. I have forgotten about modifications of names to lower
case.

The owner of a table can drop trigger using the command DROP TRIGGER.

However, where I can find information on philosophy of that approach.

For me internal triggers are marked isinternal not to be accessed using SQL
commands. Removing internals, f. e. FK triggers, by hand by a programmer and
even by an administrator seems not to be a recommended practice.

Kind Regards
Andrzej Mazurkiewicz

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2014-04-02 14:59:34 Re: using arrays within structure in ECPG
Previous Message Tom Lane 2014-04-02 14:06:29 Re: get_fn_expr_variadic considered harmful