DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com;
	h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
	b=SDgsvrp8E/U2EmsWbsbjQe4DqGL4/lhrMfCoeBpx3N0OiWKbz8xacdZ2vmTSEeTHfnRlr1R2YK9lAH337tPwJyrlhqOXYwo7YF/qMQn6420+1kTamhCIraqx2u8p9WERdxgfZaxG71BwwOeGVgD4HJp/WsT0OrEO0F1oxRU+CBg=;
References: 
 <B75CD08C73BD3543B97E4EF3964B7D701F15AD68@CITESMBX1.ad.uillinois.edu>
	<kfjgap$ouk$1@ger.gmane.org> <5124F06B.1020508@okservers.eu>
	<36037.192.168.207.54.1361375813.squirrel@webmail.etecsa.cu>
	<5124F40F.5090805@okservers.eu>
	<CAMBytETTcUR-+GyZVGJQ2X1tjVTzvHhahnh1+0qfK+vJX=gE3A@mail.gmail.com>
Message-ID: <1361471005.93321.YahooMailNeo@web162901.mail.bf1.yahoo.com>
Date: Thu, 21 Feb 2013 10:23:25 -0800 (PST)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: Pg 9.1 master-slave replication
To: Prashanth Ranjalkar <prashant.ranjalkar@gmail.com>,
	Viktor <viktor@okservers.eu>
Cc: "gilberto.castillo@etecsa.cu" <gilberto.castillo@etecsa.cu>,
	"pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
In-Reply-To: 
 <CAMBytETTcUR-+GyZVGJQ2X1tjVTzvHhahnh1+0qfK+vJX=gE3A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Prashanth Ranjalkar <prashant.ranjalkar@gmail.com> wrote:

>> Hello, Could explain somebody what will happen, if the slave

> It depends on the type of replication is used.
>
> If it's a slony replication then master continues to work and
> will catch up when slave is available.
>
> However if the Streaming replication is used, [...] once it fills
> all the space, master may go down.

That strikes me a false distinction -- Slony also stores data to be
replicated until the slave becomes available.=A0 Either way you can
control where that is stored, and you need to watch out for space
problems on an extended outage of a replica.

An issue I don't think I've seen mentioned is that if you use
synchronous replication you are telling PostgreSQL not to return an
indication of success for a data-modifying transaction until the
work of that transaction has been persisted on at least one
replica.=A0 To avoid stalls on the master, you may want to define
multiple synchronous replicas, so that when one goes down you keep
running without DBA intervention.

--=20
Kevin Grittner
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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