On Mon, Apr 14, 2014 at 03:14:46PM -0600, Jason Mathis wrote:
> Just keep in mind that while wal archiving and replication sound very similar they are intended for two different
things.??
>
> Wal Archiving = backup/DR/PITR/standby
> Replication = High availability/reporting??
it would be nice if the documentation reflected this.
the current information i derived, basically says to do both.
i'm looking to revise my settings to:
- nullify/NOP the archive_command and restore_command
- use the slave to do a pg_dumpall as the backup
the standby node serves as a read-only slave, which allows for some
performance gains.
the standby node could be promoted to master, should the master have issues.
the backup would allow for a recovery from a catestrophic/cascading error
(ie. drop all tables).
does this make sense?
--
Jim Mercer Reptilian Research jim@reptiles.org +1 416 410-5633
"He who dies with the most toys is nonetheless dead"
