| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | "Andrey V(dot) Lepikhov" <a(dot)lepikhov(at)postgrespro(dot)ru> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "g(dot)smolkin(at)postgrespro(dot)ru" <g(dot)smolkin(at)postgrespro(dot)ru> |
| Subject: | Re: [PATCH] Timestamp for a XLOG_BACKUP_END WAL-record |
| Date: | 2018-07-10 17:26:06 |
| Message-ID: | CAHGQGwHSdFafrAEAW6Jep_XLnGBNsFJkDf1gYar6fAoPU=AdFQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jul 10, 2018 at 6:41 PM, Andrey V. Lepikhov
<a(dot)lepikhov(at)postgrespro(dot)ru> wrote:
>
>
> On 10.07.2018 06:45, Andres Freund wrote:
>>
>> Hi,
>>
>> On 2018-07-10 06:41:32 +0500, Andrey V. Lepikhov wrote:
>>>
>>> This functionality is needed in practice when we have to determine a
>>> recovery time of specific backup.
>>
>>
>> What do you mean by "recovery time of specific backup"?
>>
>
> recovery time - is a time point where backup of PostgreSQL database instance
> was made.
> Performing database recovery, we want to know what point in time the
> restored database will correspond to.
> This functionality refers to improving the usability of pg_basebackup and
> pg_probackup utilities.
Why don't you use a backup history file for that purpose?
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emre Hasegeli | 2018-07-10 17:36:39 | _isnan() on Windows |
| Previous Message | Pavel Stehule | 2018-07-10 17:16:11 | Re: [HACKERS] plpgsql - additional extra checks |