[Pgpool-general] What is the recommended way to migrate a DB to replicate it with pgpool

[Christian Nolte]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Felix J. Ogris schrieb:
> Hi,
>  
>> I have a huge DB here which I would like to replicate with pgpool.
>> pgpool is configured for replication with two (backend-) servers. This
> 
> I am pretty much sure, but you can not replicate backends with pgpool
> directly.
> 
>>   $ pg_dump -d to_be_replicated -h host_to_be_replicated -o -F c | \
>>     pg_restore -d replicated_db -h host_replicated
> 
> Bad idea. Either you have to disable the source backend for normal user
> access, or the destination backend might have outdated data after the
> dump/restore has finished. If source and dest backend are the same hardware
> (eg. both x86), you can synchronize them using write ahead logging.
> Suggested steps are:

Let's say the postgresql admin is the only user active on the source
backend during the replication. As WAL is already enabled on that host I
guess a server restart would make sure that the tx-logs are synced, or
am I wrong here? Would a dump ( made to the destination backend (not
using pgpool, but directly through postgresql) then be save, or is the
WAL-method you've described necessary for some other reason?

- --
   For more than 4 generations the IT Professionals were the
   guardians of quality and stability in software. Before the
   dark times.	Before Microsoft...
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFGufj7CNjA0nfhW7wRAk6gAKDSpnG3yUXbNGM2Z8VsA4QEOLcsRwCfc1Lc
wD9mx06nXqEAxE0XRoyMg7k=
=aL/z
-----END PGP SIGNATURE-----