From: Adam Lang <aalang@rutgersinsurance.com>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Daryl Chance <dchance@valuedata.net>
Cc: pgsql-general@postgresql.org
Subject: Re: replication
Date: Thu, 21 Sep 2000 13:42:23 -0400
Message-ID: <002701c023f3$4cb613c0$330a0a0a@Adam> (raw)
References: <Pine.BSF.4.10.10009210954410.62098-100000@megazone23.bigpanda.com>
Well, if I end up needing to do something with it, I'll get back to the list
on ideas/solutions I encountered and see about potential pitfalls.
Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
----- Original Message -----
From: "Stephan Szabo" <sszabo@megazone23.bigpanda.com>
To: "Daryl Chance" <dchance@valuedata.net>
Cc: <pgsql-general@postgresql.org>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-general@postgresql.org
Cc: aalang@rutgersinsurance.com, sszabo@megazone23.bigpanda.com, dchance@valuedata.net
Subject: Re: replication
In-Reply-To: <002701c023f3$4cb613c0$330a0a0a@Adam>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox