pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Ribe <scott_ribe@elevated-dev.com>
To: Murthy Nunna <mnunna@fnal.gov>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Cascade Standby Configuration in 9.2.4
Date: Tue, 1 Apr 2014 17:48:55 -0600
Message-ID: <53779B8A-7926-4C62-BABE-A6811B6CBF6D@elevated-dev.com> (raw)
In-Reply-To: <BD7563973EF8894D905C80593EE9A4ED35C583@MAIL01.fnal.gov>
References: <BD7563973EF8894D905C80593EE9A4ED35C500@MAIL01.fnal.gov>
	<89222FC3-0F4E-436E-93A5-A68F19F83011@elevated-dev.com>
	<BD7563973EF8894D905C80593EE9A4ED35C583@MAIL01.fnal.gov>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>

On Apr 1, 2014, at 5:20 PM, Murthy Nunna <mnunna@fnal.gov> wrote:

> Thanks for the clarification Scott... What is the restore_command in recovery.conf does in case of streaming replication if it doesn't need logs available locally on the slave machine.

It copies the files. It has no way of knowing whether or not there's a WAL-shipping replica out there somewhere which needs them.

> Do you think if the streaming falls behind, then slave will request master to ship logs??????

The slave does not request the master to ship logs. The slave, when started uses the WAL files it finds in its locally-available WAL archive, then starts streaming from the master, which requires that there not be a gap between its local copies and what's still available on the master.

This is all covered in the documentation:

<http://www.postgresql.org/docs/9.2/static/high-availability.html;

-- 
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice






-- 
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 (4+ messages)

Message-ID: <53779B8A-7926-4C62-BABE-A6811B6CBF6D@elevated-dev.com>
Permalink:  ../53779B8A-7926-4C62-BABE-A6811B6CBF6D@elevated-dev.com/
Also on:    postgresql.org/message-id/53779B8A-7926-4C62-BABE-A6811B6CBF6D@elevated-dev.com

 · 

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: scott_ribe@elevated-dev.com, mnunna@fnal.gov
  Subject: Re: Cascade Standby Configuration in 9.2.4
  In-Reply-To: <53779B8A-7926-4C62-BABE-A6811B6CBF6D@elevated-dev.com>

* 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