| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Cascading replication and recovery_target_timeline='latest' |
| Date: | 2012-09-05 17:08:43 |
| Message-ID: | 5047871B.4040005@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05.09.2012 07:55, Dimitri Fontaine wrote:
> Heikki Linnakangas<hlinnaka(at)iki(dot)fi> writes:
>> I was worried about that too at first, but Fujii pointed out that's OK: see
>> last paragraph at
>> http://archives.postgresql.org/pgsql-hackers/2012-08/msg01203.php.
>
> Mmm, ok.
>
> I'm worried about master-standby-standby setup where the master
> disappear, we promote a standby and the second standby now feeds from
> the newly promoted standby. Well we have to reconnect manually in this
> case, but don't we need some similar stopgaps?
The second standby will have to reconnect, but it will happen automatically.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-09-05 17:15:52 | Re: plperl sigfpe reset can crash the server |
| Previous Message | Tom Lane | 2012-09-05 16:00:18 | Re: Proof of concept: standalone backend with full FE/BE protocol |