Re: Postgres Synchronous replication - Mailing list pgsql-admin

From Keith
Subject Re: Postgres Synchronous replication
Date
Msg-id CAHw75vsB2w+FB-K9dLzFX-4EOEQmLsifq_2wiG9E-rKXu67U9g@mail.gmail.com
Whole thread Raw
In response to Re: Postgres Synchronous replication  (Scott Ribe <scott_ribe@elevated-dev.com>)
Responses Re: Postgres Synchronous replication
List pgsql-admin


On Thu, May 21, 2015 at 4:29 PM, Scott Ribe <scott_ribe@elevated-dev.com> wrote:
On May 21, 2015, at 2:10 PM, Ravi Krishna <sravikrishna3@gmail.com> wrote:
>
> Every time the primary crashes…

While I agree it’s a limitation, in 14 years I’ve not seen PG crash once.


--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(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

It's not just an issue of crashing, it's an issue of failover in general, which happens quite often in high-availability scenarios. Unless a second slave is available, it can be a bit nerve-racking after you failover due to some network or system issue, you've only got a single postgres instance up for your application until you rebuild the old one.

pgsql-admin by date:

Previous
From: Keith
Date:
Subject: Re: Postgres Synchronous replication
Next
From: Ravi Krishna
Date:
Subject: Re: Postgres Synchronous replication