Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WZon9-0003LZ-Dp for pgsql-admin@arkaria.postgresql.org; Mon, 14 Apr 2014 21:51:51 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WZon8-0002b3-SC for pgsql-admin@arkaria.postgresql.org; Mon, 14 Apr 2014 21:51:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WZon7-0002Zt-Mf for pgsql-admin@postgresql.org; Mon, 14 Apr 2014 21:51:49 +0000 Received: from mailbox.reptiles.org ([198.96.117.3]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WZon4-0001ze-QG for pgsql-admin@postgresql.org; Mon, 14 Apr 2014 21:51:49 +0000 Received: from localhost by mailbox.reptiles.org via sendmail with STDIO (1767 bytes) (sender: ) (ident using UNIX) id for ; Mon, 14 Apr 2014 17:51:43 -0400 (EDT) (Smail-3.2.0.121 2005-Nov-17 #10 built 2010-Jul-16) Date: Mon, 14 Apr 2014 17:51:43 -0400 From: Jim Mercer To: Jason Mathis Cc: Scott Whitney , Scott Whitney , pgsql-admin@postgresql.org Subject: Re: streaming replication - pgsql 9.2.3 Message-ID: <20140414215143.GA38476@reptiles.org> References: <20140414163956.GA27624@reptiles.org> <2125585511.76278.1397494671973.JavaMail.zimbra@mail.int.journyx.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -2.9 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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