Re: Postgres Synchronous replication

On Thu, May 21, 2015 at 4:29 PM, Scott Ribe <scott_ribe(at)elevated-dev(dot)com>
wrote:

> On May 21, 2015, at 2:10 PM, Ravi Krishna <sravikrishna3(at)gmail(dot)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(at)elevated-dev(dot)com
> http://www.elevated-dev.com/
> https://www.linkedin.com/in/scottribe/
> (303) 722-0567 voice
>
>
>
>
>
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)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.