There's also PostgreSQL Replicator (which I haven't gotten around to
trying) :
http://pgreplicator.sourceforge.net
:-)
Regards and best wishes,
Justin Clift
Allan Engelhardt wrote:
>
> Ehhh, use dual-ported RAID disks? (Well, tri-port in your case, but maybe A and B machines are enough. You still
havea (small) single point of failure, but you probably have that anyhow (network switch?). You'll need some way of
briningPostgreSQL up on B when A dies, but that could be a simple script. Reconnect would of course be manual from the
pointof the client.).
>
> Or buy Oracle.
>
> Replication is at the top of the TODO list: http://www.uk.postgresql.org/docs/todo.html
>
> Allan.
>
> PS:
> Maybe SQLB does some of what you want? http://sourceforge.net/projects/sqlb/ [The documentation is a little
opaque...I'mnot quite sure what it does, exactly. Anybody want to comment?]
>
> Raymond Chui wrote:
>
> > Does the latest PostgreSQL 7.1.2 support database mirroring?
> >
> > I have machine A, B and C, they all have the same database and tables.
> > Machine A is the operational machine, machine B and C are backup.
> >
> > If users do INSERT, UPDATE and DELETE in machine A, I want have the
> > same SQL statements in machine B and C.
> >
> > 1. I can do pg_dump or COPY every hour.
> > 2. I can use PerlDBI or JDBC open multiple connections for each SQL
> > statement.
> > 3. But I prefer if the system auto mirroring the database, then I can do
> > nothing.
> > All I need is set the auto mirroring configure.
> >
> > Please tell me how to do in 3. above. Thank you in advance!
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
