Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tzxz4-0006NP-RK for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jan 2013 23:19:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1Tzxz3-0001GC-8B for pgsql-hackers@arkaria.postgresql.org; Mon, 28 Jan 2013 23:19:25 +0000 Received: from makus.postgresql.org ([98.129.198.125]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tzxz1-0001Fz-F1 for pgsql-hackers@postgresql.org; Mon, 28 Jan 2013 23:19:23 +0000 Received: from acidenitrix.villemain.org ([91.121.90.165]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Tzxyz-0004tJ-Vh for pgsql-hackers@postgresql.org; Mon, 28 Jan 2013 23:19:22 +0000 Received: from [89.157.243.170] (helo=Dimitris-MacBook-Air.local) by acidenitrix.villemain.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.72) (envelope-from ) id 1Tzxyy-00012n-0G; Tue, 29 Jan 2013 00:19:20 +0100 From: Dimitri Fontaine To: Christopher Browne Cc: PostgreSQL Hackers Subject: Re: Event Triggers: adding information Organization: 2ndQuadrant References: <20130104205251.GB9191@alvh.no-ip.org> <20130109165829.GB4490@alvh.no-ip.org> User-Mail-Address: dimitri@2ndQuadrant.fr Date: Tue, 29 Jan 2013 00:19:07 +0100 In-Reply-To: (Christopher Browne's message of "Mon, 28 Jan 2013 18:07:32 -0500") Message-ID: User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.2 (darwin) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org Christopher Browne writes: > I'm poking at event triggers a bit; would like to set up some examples > (and see if they > work, or break down badly; both are interesting results) to do some > validation of schema > for Slony. Cool, thanks! > What I'm basically thinking about is to set up some event triggers that r= un on > DROP TABLE / DROP SEQUENCE, and see about cleaning up the replication > side of things (e.g. - inject a request to drop the table/sequence > from replication). Sure. In what got commited from the current patch series, you will only know that a DROP TABLE (or DROP SEQUENCE) occured, and we're trying to get to an agreement with Robert if we should prefer to add visibility to such events that occurs in a CASCADE statement or rather add the OID (and maybe the name) of the Object that's going to be dropped. Your opinion is worth a lot on that matter, if you have one to share!=C2=A0= :) > I have a bit of a complaint as to what documentation is included; I don't= see > any references in the documentation to ddl_command_start / ddl_command_en= d, > which seem to be necessary values for event triggers. What we have now here: http://www.postgresql.org/docs/devel/static/event-trigger-matrix.html http://www.postgresql.org/docs/devel/static/sql-createeventtrigger.html http://www.postgresql.org/docs/devel/static/plpgsql-trigger.html#PLPGSQL-= EVENT-TRIGGER Is it not visible enough, or really missing the point? > I'd tend to think that there should be a new subsection in the "man page"= for > CREATE TRIGGER that includes at least two fully formed examples of event > triggers, involving the two events in question. Is change of that > sort in progress? The event triggers are addressed in a whole new chapter of the docs, maybe that's why you didn't find the docs? --=20 Dimitri Fontaine http://2ndQuadrant.fr PostgreSQL : Expertise, Formation et Support --=20 Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers