Re: Immediate standby promotion - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Immediate standby promotion
Date
Msg-id CAFcNs+ofS8aqDN+TbnvZ5JBb2NTfWOo+7uNTF67ebO432W=hHA@mail.gmail.com
Whole thread
In response to Re: Immediate standby promotion  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Immediate standby promotion
List pgsql-hackers

On Thu, Aug 14, 2014 at 4:27 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> We already have the facilities to stop replay at a defined place.  But
> then what?  Without this patch, do well tell the customer to stop
> replay, do a pg_dump of the whole database, and restore it into a new
> database?  Because that's crazy.
>

Yeah... and as Fujji already said another case is when some operation error occurs in the master (like a wrong "drop database") and we have a time-delayed standby that can be used to recover the mistake quickly.


--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ALTER TABLESPACE MOVE command tag tweak
Next
From: Tomas Vondra
Date:
Subject: Re: 9.5: Memory-bounded HashAgg