X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 81A54D1B502 for ; Sun, 14 Sep 2003 10:29:22 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 08763-07 for ; Sun, 14 Sep 2003 07:28:52 -0300 (ADT) Received: from web21403.mail.yahoo.com (web21403.mail.yahoo.com [216.136.232.73]) by svr1.postgresql.org (Postfix) with SMTP id 05B61D1B4FB for ; Sun, 14 Sep 2003 07:28:49 -0300 (ADT) Message-ID: <20030914102851.82497.qmail@web21403.mail.yahoo.com> Received: from [64.81.205.234] by web21403.mail.yahoo.com via HTTP; Sun, 14 Sep 2003 03:28:51 PDT Date: Sun, 14 Sep 2003 03:28:51 -0700 (PDT) From: ow Subject: Re: A generic trigger? To: Peter Childs , pgsql-sql@postgresql.org In-Reply-To: <200309140926.50281.Blue.Dragon@blueyonder.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200309/120 X-Sequence-Number: 15098 --- Peter Childs wrote: > Yes it is possible and I've done it. The reason I'm not using it is because > I > wrote it in Pl/Python and if you attach the same trigger to more than one > table in the same transaction pg/python (actually the entire server crashes > but thats not the point) crashes. Well it did when I last tested it in early > versions. I'm still thinking of getting around to rewriting it in a language > without this bug, since nobody sounds like they are going to fix it. C might > be best! [snip] Hi, In my case, "company" and "company_backup" tables have the *same* structure, so I was hoping for a simpler solution using just plpgsql. Any ideas? Thanks __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com