Received: from localhost (maia-2.hub.org [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 331469FB6E1 for ; Wed, 18 Jul 2007 13:31:06 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 77751-09 for ; Wed, 18 Jul 2007 13:30:55 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from ag-out-0708.google.com (ag-out-0708.google.com [72.14.246.242]) by postgresql.org (Postfix) with ESMTP id 0091E9FB924 for ; Wed, 18 Jul 2007 13:30:59 -0300 (ADT) Received: by ag-out-0708.google.com with SMTP id 23so321675agd for ; Wed, 18 Jul 2007 09:30:59 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=ZqjH/OCOIH3EdP/8J+EoB0oKc6n0HmerpoJNEYwk5uQQNevr9c3unoWn3mDEyhrtOXKe8YjsVGD23EZbE4fY926/ofprt23aqofKTm2KzthbvmK5sUOjWykuoJKSJulFAcws/kqu4UPNtl6ZRucSnzZl6M4jEyFhcGFO9lx16Ks= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=N59Zb2+owTTjyLNyX95MkawAPVIDKWDrwzuLpBFEepIl+CX2JkcPFX2jCdgxbO/c1YhIzKyKhPR9MretUz0BhJeMjmHqKP+1+Y7rPYLoK7mb5t+5Fd/4YZrxTlLXTDbPPAqvSLnqiOFyyeA4HH06mkkPQBn6vw6HmwfFpRz+XmQ= Received: by 10.114.166.1 with SMTP id o1mr1644350wae.1184776256780; Wed, 18 Jul 2007 09:30:56 -0700 (PDT) Received: by 10.114.174.13 with HTTP; Wed, 18 Jul 2007 09:30:56 -0700 (PDT) Message-ID: Date: Wed, 18 Jul 2007 12:30:56 -0400 From: "Michael Dengler" To: "Tom Lane" Subject: Re: How to use a trigger to write rows to a remote server Cc: pgsql-performance@postgresql.org In-Reply-To: <18352.1184770316@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_92962_2046706.1184776256718" References: <18352.1184770316@sss.pgh.pa.us> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200707/220 X-Sequence-Number: 25904 ------=_Part_92962_2046706.1184776256718 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hmm..I was hoping to avoid personal insults.... Anyway, Nuts or not...what I am attempting is to simply have row from one table inserted into another servers DB I don't see it as replication because: a) The destination table will have a trigger that modifies the arriving data to fit its table scheme. b) It is not critical that the data be synchronous (ie a lost row on the destination DB is not a big deal) c) I see as more of a provision of data to the destination DB NOT A REPLICATION OF DATA. Essentially the remote server just wants to know when some record arrives at the source server and wants to know some of the info contained in the new record. And yes it may be that I know little about the myriad of problems involved with replication...but I do know how to carry on a civil, adult conversation....maybe we can have a knowledge exchange. Cheers Mike On 7/18/07, Tom Lane wrote: > > "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 > ------=_Part_92962_2046706.1184776256718 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hmm..I was hoping to avoid personal insults....

Anyway, Nuts or not...what I am attempting is to simply have row from one table inserted into another servers DB I don't see it as replication because:

a) The destination table will have a trigger that modifies the arriving data to fit its table scheme.
b) It is not critical that the data be synchronous (ie a lost row on the destination DB is not a big deal)
c) I see as more of a provision of data to the destination DB NOT A REPLICATION OF DATA.

Essentially the remote server just wants to know when some record arrives at the source server and wants to know some of the info contained in the new record.

And yes it may be that I know little about the myriad of problems involved with replication...but I do know how to carry on a civil, adult conversation....maybe we can have a knowledge exchange.

Cheers

Mike



On 7/18/07, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Michael Dengler" <michael.dengler@gmail.com> 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

------=_Part_92962_2046706.1184776256718--