Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 10B7C9552D4 for ; Tue, 28 Feb 2012 11:04:17 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1S2Ob9-0005mF-D2 for pgsql-hackers@postgresql.org; Tue, 28 Feb 2012 15:04:16 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id q1SF3vTF004966; Tue, 28 Feb 2012 10:03:58 -0500 (EST) To: Thom Brown cc: Dimitri Fontaine , PostgreSQL Hackers Subject: Re: Command Triggers, patch v11 In-reply-to: References: Comments: In-reply-to Thom Brown message dated "Tue, 28 Feb 2012 11:43:54 +0000" Date: Tue, 28 Feb 2012 10:03:57 -0500 Message-ID: <4965.1330441437@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -1.9 (-) X-Archive-Number: 201202/1392 X-Sequence-Number: 203756 Thom Brown writes: > Well the problem is that you can add commands to a trigger en masse, > but you can only remove them one at a time. Couldn't we at least > allow the removal of multiple commands at the same time? The docs you > wrote suggest you can do this, but you can't. This seems over-complicated. Triggers on tables do not have alterable properties, why should command triggers? I vote for CREATE COMMAND TRIGGER name ... properties ...; DROP COMMAND TRIGGER name; full stop. If you want to run the same trigger function on some more commands, add another trigger name. regards, tom lane