Here you can get the latest tarball of PostgreSQL Replicator
Version |
Release Date |
Description |
---|---|---|
14/02/2001 |
First public release |
|
19/06/2001 |
New minor release, tested with PostgreSQL-7.1.2 |
|
15/10/2001 |
New Release supporting Large Object Replication |
Updating pgReplicator to a new version
Assuming pgReplicator was installed in /home/replicator as reported in Installation tutorial:
download the latest version of pgreplicator tarball in /home/replicator
move pgreplica directory to pgreplica-old-version
untar the new tarball
restart pgrd daemon (assuming no replication process is running)
Notes
To replicate postgres databases, pgReplicator works at two distinct levels:
a set of tables, functions and triggers are created into postgres database to capture local users operations
a pgrd daemon must be running on different sites on a WAN to propagate local operations for database synchronization
A new pgReplicator release usually have changes in both daemon source code and postgres functions and triggers code.
After updating old pgreplica directory with the new one,
new pgrd features will be available simply restarting the
daemon; on the contrary new functions and triggers will be available
for new replicated databases only.
To update trigger functions in
previously replicated databases you may use the update_triggers.tcl
script in utilities
directory.
pgReplicator reads into /etc/pgr.conf
file for configuration.
Usually new releases add some other
internal variable to pgr.conf file so you must copy new
pgr.conf from pgreplica to /etc and reconfigure it.