| From: | Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Immediate standby promotion |
| Date: | 2014-08-14 19:36:42 |
| Message-ID: | CAFcNs+ofS8aqDN+TbnvZ5JBb2NTfWOo+7uNTF67ebO432W=hHA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 14, 2014 at 4:27 PM, Robert Haas <robertmhaas(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2014-08-14 19:47:58 | Re: 9.5: Memory-bounded HashAgg |
| Previous Message | Robert Haas | 2014-08-14 19:31:49 | Re: ALTER TABLESPACE MOVE command tag tweak |