From: | Daniel Farina <daniel(at)heroku(dot)com> |
---|---|
To: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
Cc: | Daymel Bonne Solís <dbonne(at)uci(dot)cu>, postgres-devel <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: system_information.triggers & truncate triggers |
Date: | 2012-09-26 07:08:29 |
Message-ID: | CAAZKuFZCjAtFqFY4G-if0eS_CSEa1VnL6vr2-cRq1LeqGckO2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 25, 2012 at 10:55 PM, Jaime Casanova <jaime(at)2ndquadrant(dot)com> wrote:
> On Wed, Sep 26, 2012 at 12:17 AM, Daymel Bonne Solís <dbonne(at)uci(dot)cu> wrote:
>> Hello hackers:
>>
>> I need a list of all triggers created in my database, but the view
>> system_information.triggers does not show truncate triggers, but it does for
>> insert, update and delete triggers.
>>
>> The same problem is found in versions 9.1 and 9.2.
>>
>
> The definition of information_schema.triggers contains this:
> """
> FROM pg_namespace n, pg_class c, pg_trigger t,
> -- hard-wired refs to TRIGGER_TYPE_INSERT, TRIGGER_TYPE_DELETE,
> -- TRIGGER_TYPE_UPDATE; we intentionally omit TRIGGER_TYPE_TRUNCATE
> (VALUES (4, 'INSERT'),
> (8, 'DELETE'),
> (16, 'UPDATE')) AS em (num, text)
> """
>
> so it seems that we are not showing TRUNCATE triggers intentionally,
> but that comment fails to explain why
Wouldn't it be because TRUNCATE is a PostgreSQL language extension?
--
fdr
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-09-26 07:14:19 | Re: htup header reorganization breaks many extension modules |
Previous Message | Devrim GÜNDÜZ | 2012-09-26 06:46:32 | Re: [COMMITTERS] pgsql: Properly set relpersistence for fake relcache entries. |