From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp> |
Cc: | magnus(at)hagander(dot)net, heikki(dot)linnakangas(at)enterprisedb(dot)com, ssinger_pg(at)sympatico(dot)ca, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Online base backup from the hot-standby |
Date: | 2011-07-05 05:54:18 |
Message-ID: | CAHGQGwGHUV4C99CC1xddcStJNQ9gb-tHg5J7+o1q+gAabt27Vw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2011/7/4 Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp>:
>
>> When the standby restarts after it crashes during recovery, it always
>> checks whether recovery has reached the backup end location by
>> using minRecoveryPoint even though the standby doesn't start from
>> the backup. This looks odd.
>
> Certainly.
>
> But, in this case, the state before recovery starts is lost.
> Therefore, postgres can not see that the backup got from whether
> standby server or master.
>
> What should?
> Should use pg_control?
> Ex.
> * Add 'Where to get backup' to pg_control. (default 'none')
> * When recovery starts, it checks it whether 'none'.
> * When minRecoveryPoint equals 0/0, change 'master'.
> * When minRecoveryPoint do not equals 0/0, change 'slave'.
> * When it reached the end of recovery, change 'none' .
What about using backupStartPoint to check whether this recovery
started from the backup or not?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Brar Piening | 2011-07-05 06:30:06 | Re: %ENV warnings during builds |
Previous Message | Fujii Masao | 2011-07-05 03:34:58 | Re: Cascade replication |