On 2014-02-24 12:45:12 -0500, Bruce Momjian wrote: > 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.
Thanks. It'd have been nice tho, to mention FabrÃzio in the commit message as the patch's author. Greetings, Andres Freund -- Andres Freund http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
