Received: from [203.3.121.10] (jafar.unixpac.com.au [203.3.121.10]) by postgresql.org (8.11.3/8.11.4) with SMTP id fATLs2m33559; Thu, 29 Nov 2001 16:54:03 -0500 (EST) (envelope-from peterh@600ml.com.au) Received: from no.name.available by [203.3.121.10] via smtpd (for postgresql.org [64.49.215.8]) with SMTP; 29 Nov 2001 21:58:02 UT Received: from 600mlPeterPC1 (localhost.localdomain [127.0.0.1]) by eeyore.unixpac.com.au (Postfix) with SMTP id 29C04234EC; Fri, 30 Nov 2001 08:52:48 +1100 (EST) Message-ID: <003e01c1791f$75210590$0300000a@600mlPeterPC1> Reply-To: "Peter" From: "Peter" To: , References: <5.0.2.1.0.20010418223233.00a68170@mail.e-magine.com.au> <20010418073430.B12408@cc.usu.edu> <20010418164436.A41431@ilse.nl> <20010418085424.A13383@cc.usu.edu> <20010418173727.A5021@rakete.joerdens.de> <20010418202814.B16143@ilse.nl> <20011119083547.A22031@cc.usu.edu> Subject: Database Replicatio via triggers Date: Fri, 30 Nov 2001 08:47:35 +1100 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.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 X-Archive-Number: 200111/134 X-Sequence-Number: 775 Hi there again, we are setting up a small cluster with loadbalancing, fail-over, etc - 2 front and 2 back-end db servers. Everything is ok except for database replication. As I understand it the easiest way of replicating the database is via triggers; as rows in a table gets updated, deleted or are inserted the same action is triggered on the second db server. My question is: Does the trigger function allow for database level triggers or is it only possible for individual tables? Also has anyone got experience with this kind of situation and is this idea generaly commendable? thanks in advance regards, Peter