pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Mercer <jim@reptiles.org>
To: Jason Mathis <jmathis@redzonesoftware.com>
Cc: Scott Whitney <scott@journyx.com>
Cc: Scott Whitney <swhitney@journyx.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: streaming replication - pgsql 9.2.3
Date: Mon, 14 Apr 2014 17:51:43 -0400
Message-ID: <20140414215143.GA38476@reptiles.org> (raw)
In-Reply-To: <etPan.534c4fc7.3d1b58ba.226e@palos>
References: <20140414163956.GA27624@reptiles.org>
	<2125585511.76278.1397494671973.JavaMail.zimbra@mail.int.journyx.com>
	<etPan.534c4fc7.3d1b58ba.226e@palos>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

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"


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



view thread (8+ messages)  latest in thread

Message-ID: <20140414215143.GA38476@reptiles.org>
Permalink:  ../20140414215143.GA38476@reptiles.org/
Also on:    postgresql.org/message-id/20140414215143.GA38476@reptiles.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: jim@reptiles.org, jmathis@redzonesoftware.com, scott@journyx.com, swhitney@journyx.com
  Subject: Re: streaming replication - pgsql 9.2.3
  In-Reply-To: <20140414215143.GA38476@reptiles.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox