Taras Kopets wrote:
Hi!
I think you should try to use triggers with
dbi-linkhttp://pgfoundry.org/projects/dbi-link/to achieve this.
AFAIK there is no such replication with other RDBMS as you need.
Taras Kopets
Seems like I introduced a small misunderstanding here. The data doesn't
I'd start with something fairly straightforward. dbmirror
is very simple but does a lot. There are two parts:
A trigger function and set of database tables to collect
replication data. The trigger function is written is 'C' and
performance is good.
The second part is a Perl script that attaches
On Friday 27 October 2006 09:59, Alban Hertroys wrote:
Hello list,
We're investigating a ways to replicate changes to the database to
several outside systems.
Some filtering will need to take place, as not all changes are allowed
to go to all systems. Whether the system receiving the
On Fri, Oct 27, 2006 at 03:59:02PM +0200, Alban Hertroys wrote:
2.) Use one of the existing replication systems. We're currently under
the impression that (we've looked at Slony-I particularly) the slave
system is supposed to be another (postgresql?) database. This wouldn't
fit our needs,
Hello list,
We're investigating a ways to replicate changes to the database to
several outside systems.
Some filtering will need to take place, as not all changes are allowed
to go to all systems. Whether the system receiving the changes stores
them in a database or not isn't particularly
Hi!I think you should try to use triggers with dbi-link to achieve this.AFAIK there is no such replication with other RDBMS as you need.Taras Kopets
On 10/27/06, Alban Hertroys [EMAIL PROTECTED] wrote:
Hello list,We're investigating a ways to replicate changes to the database toseveral outside
