Adrian von Bidder wrote:
I don't know the rpm builds you're using; the
Debian packages allow configuring two instances on two different ports
AFAIK. Possibly the rpm installation do, too. Even if not: hacking up a
2nd start script which runs postgres against a different data directory /
conf
[continuous backup]
On Tuesday 15 June 2010 21.42:52 Oliver Kohll - Mailing Lists wrote:
> 1) Continuously ship the WAL records to somewhere on the test server
> unknown to Postgres but run the test machine as a normal database
> completely separately. If a backup is needed, delete the test databa
On Tuesday, June 15, 2010, "Oliver Kohll - Mailing Lists"
wrote:
> Are either of those two likely? Any other suggestions? Another question
> is will the replication coming in v9.0 change things and would it be
> worth holding off until then? In particular Command Prompt's PITR tools
> look useful
Hello,
I'm interested in using WAL shipping / replication for backup purposes but have
no interest in failover. Currently my situation is:
I have two servers, live and backup, which are in different cities. The backup
server is also a test/development machine.
Backups of my most important data
