Here you can get the latest tarball of PostgreSQL Replicator


Release Date




First “public” release



New minor release, tested with PostgreSQL-7.1.2



New Release supporting Large Object Replication

Updating pgReplicator to a new version

Assuming pgReplicator was installed in /home/replicator as reported in Installation tutorial:

  1. download the latest version of pgreplicator tarball in /home/replicator

  2. move pgreplica directory to pgreplica-old-version

  3. untar the new tarball

  4. restart pgrd daemon (assuming no replication process is running)


To replicate postgres databases, pgReplicator works at two distinct levels:

  1. a set of tables, functions and triggers are created into postgres database to capture local users operations

  2. 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.