Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 121C69FB560 for ; Wed, 18 Jul 2007 11:52:04 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 04289-10 for ; Wed, 18 Jul 2007 11:52:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3E39E9FB555 for ; Wed, 18 Jul 2007 11:52:00 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l6IEpuWA018353; Wed, 18 Jul 2007 10:51:57 -0400 (EDT) To: "Michael Dengler" cc: pgsql-performance@postgresql.org Subject: Re: How to use a trigger to write rows to a remote server In-reply-to: References: Comments: In-reply-to "Michael Dengler" message dated "Wed, 18 Jul 2007 09:36:33 -0400" Date: Wed, 18 Jul 2007 10:51:56 -0400 Message-ID: <18352.1184770316@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/215 X-Sequence-Number: 25899 "Michael Dengler" writes: > I am trying to find out how to use a trigger function on a table to copy any > inserted row to a remote PG server. > ... > This is not replication, I'm not interested in a full blown trigger based > replication solution. To be blunt, you're nuts. You *are* building a trigger based replication system, and the fact that you think you can cut corners just shows how little you know about the problems involved. Use Slony, or some other solution that someone else has already gotten the bugs out of. regards, tom lane