| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com>, mailings(at)oopsware(dot)de |
| Subject: | Re: psql should show disabled internal triggers |
| Date: | 2014-02-24 17:45:12 |
| Message-ID: | 20140224174512.GD16943@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Feb 12, 2014 at 09:04:45PM -0500, Bruce Momjian wrote:
> As others, I am concerned about people being confused when funny-looking
> trigger names suddenly appearing when you disable all table triggers.
>
> What I ended up doing is to create a user and internal section when
> displaying disabled triggers:
>
> Disabled user triggers:
> check_update BEFORE UPDATE ON orders FOR EACH ROW EXECUTE PROCEDURE trigf()
> Disabled internal triggers:
> "RI_ConstraintTrigger_c_16409" AFTER INSERT ON orders FROM customer NOT DEF ...
> "RI_ConstraintTrigger_c_16410" AFTER UPDATE ON orders FROM customer NOT DEF ...
>
> I kept the "Triggers" section unchanged, showing only user triggers. I
> also updated the code to handle 8.3+ servers.
>
> Patch attached.
Patch applied.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-02-24 17:50:03 | Re: Changeset Extraction v7.6.1 |
| Previous Message | Robert Haas | 2014-02-24 17:38:15 | Re: Minor performance improvement in transition to external sort |