> Some time back I discussed the inclusion of replication (e.g.
> postgres-R) into postgres.
> One of the technical reasons that I understand against such a move is
> the application dependence of replication. PostgresR requires a large
> amount of code change in postgres.
> All this leads to a bitter taste in the minds of my managers who want
> to use postgres but can't do without replication, and also they want
> to only rely on the main dev path of postgres itself.
Try using Slony, it's actually up to date:
http://www.slony.info/
Chris
