Hi,
Use one of the existent replication systems
http://wiki.postgresql.org/wiki/Replication,_Clustering,_and_Connection_Pooling#Replication
p.s. I would highlight Slony, Londiste and Bucardo.
On 11 June 2010 14:11, Ulas Albayrak wrote:
> Hi,
>
>
>
> I’m in the process of moving our production
Hi,
I'm in the process of moving our production database to a different physical
server, running a different OS and a newer release of postgreSQL. My problem is
that I'm not really sure how to go about it.
My initial idea was to use WAL archiving to reproduce the db on the new server
and then
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> My best idea so far is to do a pg_dump and somehow archive all the DML
> in the original db from that point in time for later insertion in the
> new db, but I dont know how that would be done practically. And I
> dont even know if thats the be
On 11/06/2010 11:24, Ulas Albayrak wrote:
> My initial idea was to use WAL archiving to reproduce the db on the
> new server and then get it up to date with the logs from the time of
> base backup creation to the time the new server can get up. That was
> until I found out WAL archiving doesn’t wo
Hi,
I’m in the process of moving our production database to a different
physical server, running a different OS and a newer release of
postgreSQL. My problem is that I’m not really sure how to go about it.
My initial idea was to use WAL archiving to reproduce the db on the
new server and then get
