| 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 10:29:05 |
| Message-ID: | CAHGQGwEHTNLyhDL2H-gyyoZ8kpPC7zSM9um0X9sbo0iNhJ0=eg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2011/7/5 Jun Ishiduka <ishizuka(dot)jun(at)po(dot)ntts(dot)co(dot)jp>:
>
>> What about using backupStartPoint to check whether this recovery
>> started from the backup or not?
>
> No, postgres can check whether this recovery started from the backup
> or not, but can not check whether standby server or master (got backup
> from).
Oh, right. We cannot distinguish the following two cases just by using
minRecoveryPoint and backupStartPoint.
* The standby starts from the backup taken from the standby
* The standby starts after it crashes during recovering from the
backup taken from the master
As you proposed, adding new field which stores the backup end location
taken from minRecoveryPoint, into pg_control sounds good idea.
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-07-05 10:55:50 | Re: Inconsistency between postgresql.conf and docs |
| Previous Message | Peter Geoghegan | 2011-07-05 09:27:52 | Re: Latch implementation that wakes on postmaster death on both win32 and Unix |