Received: from bush.rutgersinsurance.com (IDENT:root@rutgersinsurance.com [38.138.71.194]) by hub.org (8.10.1/8.10.1) with ESMTP id e8LHdns97139 for ; Thu, 21 Sep 2000 13:39:50 -0400 (EDT) Received: from Adam ([10.10.10.51]) by bush.rutgersinsurance.com (8.9.3/8.9.3) with SMTP id NAA01824 for ; Thu, 21 Sep 2000 13:45:26 -0400 Message-ID: <001d01c023f3$314f9ca0$330a0a0a@Adam> From: "Adam Lang" To: "PGSQL General" Subject: Fw: replication Date: Thu, 21 Sep 2000 13:41:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200009/617 Adam Lang Systems Engineer Rutgers Casualty Insurance Company ----- Original Message ----- From: "Adam Lang" To: "Stephan Szabo" Sent: Thursday, September 21, 2000 1:41 PM Subject: Re: [GENERAL] replication > Plus, I don't want to replicate on a per insert/update basis. I would like > to do it as a large batch during off hours. > > Adam Lang > Systems Engineer > Rutgers Casualty Insurance Company > ----- Original Message ----- > From: "Stephan Szabo" > To: "Daryl Chance" > Cc: > Sent: Thursday, September 21, 2000 12:59 PM > Subject: Re: [GENERAL] replication > > > > On Thu, 21 Sep 2000, Daryl Chance wrote: > > > > > Could this possibly be done using triggers? I'm new to > > > postgres, but I know on a project I was doing using oracle > > > the dba could setup triggers to run on the OnInsert() (not > > > sure what it's actually called in oracle...). Do maybe > > > on the "OnInsert" of table foo you could do: > > > > > > Insert into foo@remotesite1 .... > > > > > > Is this possible in postgres? I'm looking at using postgres > > > for the next version of my SW and if replication isn't in, > > > I'm gonna need something like this :). > > > > You could probably write a C trigger that would propogate > > changes, except that there are still problems. What do you > > do when you roll back the transaction? Currently, there > > aren't triggers for transaction start and end. Triggers that > > do stuff outside the database right now are a bad idea unless > > you have some other mechanism to determine whether something > > was really supposed to be done. It could be done, but isn't > > trivial. >