Postgres Pro
Downloads
Home   >   mailing lists

Re: Promoting sync slave to master without incrementing timeline counter? - Mailing list pgsql-general

From Simon Riggs
Subject Re: Promoting sync slave to master without incrementing timeline counter?
Date
Msg-id CA+U5nMLZTEGyRcenYWKJ=ADsneHG7im_mkvSBByk_Tdp1JzbSA@mail.gmail.com
Whole thread Raw
In response to Promoting sync slave to master without incrementing timeline counter?  (David Pirotte <dpirotte@gmail.com>)
List pgsql-general
Tree view 
On 21 June 2012 16:10, David Pirotte <dpirotte@gmail.com> wrote:

> So, given a hard failure (i.e. power loss) of the master, `pg_ctl promote`
> provides availability more quickly, but `pg_ctl restart` provides data
> redundancy more quickly.

Not sure where this idea of "more quickly" comes from. Can you explain?


> Are there  risks associated with the `pg_ctl
> restart` approach, or is it safe to use?

PostgreSQL supports both, why do you mention just one of them as a
potential risk?

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

pgsql-general by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: Promoting sync slave to master without incrementing timeline counter?
Next
From: Stefan Schwarzer
Date:
Subject: Re: Error message "psql: could not connect to server: No such file or directory"