| From: | KONDO Mitsumasa <kondo(dot)mitsumasa(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | fabriziomello(at)gmail(dot)com, Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Time-Delayed Standbys |
| Date: | 2013-12-10 04:26:27 |
| Message-ID: | 52A697F3.8030403@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
(2013/12/09 20:29), Andres Freund wrote:
> On 2013-12-09 19:51:01 +0900, KONDO Mitsumasa wrote:
>> Add my comment. We have to consider three situations.
>>
>> 1. PITR
>> 2. replication standby
>> 3. replication standby with restore_command
>>
>> I think this patch cannot delay in 1 situation.
>
> Why?
I have three reasons.
1. It is written in document. Can we remove it?
2. Name of this feature is "Time-delayed *standbys*", not "Time-delayed
*recovery*". Can we change it?
3. I think it is unnessesary in master PITR. And if it can delay in master
PITR, it will become master at unexpected timing, not to continue to
recovery. It is meaningless.
I'd like to ask you what do you expect from this feature and how to use it.
Regards,
--
Mitsumasa KONDO
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2013-12-10 05:19:14 | Re: ANALYZE sampling is too good |
| Previous Message | Alvaro Herrera | 2013-12-10 04:25:20 | Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby |