Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 93DE298F705 for ; Tue, 5 Jun 2012 15:00:33 -0300 (ADT) Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Sby3U-0008Cr-U9 for pgsql-sql@postgresql.org; Tue, 05 Jun 2012 18:00:33 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1Sby3H-0003DK-Qy for pgsql-sql@postgresql.org; Tue, 05 Jun 2012 11:00:19 -0700 Date: Tue, 5 Jun 2012 11:00:19 -0700 (PDT) From: rverghese To: pgsql-sql@postgresql.org Message-ID: <1338919219829-5711310.post@n5.nabble.com> Subject: creating a new trigger for a table on a slave host MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -0.1 (/) X-Archive-Number: 201206/22 X-Sequence-Number: 36676 I need to modify my database schema and create a new trigger function. I know that triggers are suppressed on the slave once Slony starts up. However since slony is now already running on the slave, if I create a new trigger there, it will not be suppressed. What is the best practice for creating a trigger on the slave? Should you take the table out of replication, create trigger , then add the table back in? Is there some other way to do it? Thanks RV -- View this message in context: http://postgresql.1045698.n5.nabble.com/creating-a-new-trigger-for-a-table-on-a-slave-host-tp5711310.html Sent from the PostgreSQL - sql mailing list archive at Nabble.com.