Re: [PATCH] Timestamp for a XLOG_BACKUP_END WAL-record

From: Andres Freund <andres(at)anarazel(dot)de>
To: "Andrey V(dot) Lepikhov" <a(dot)lepikhov(at)postgrespro(dot)ru>
Cc: 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 01:45:43
Message-ID: 20180710014543.d75tedc32tknz33a@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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"?

> This code developed in compatibility with WAL segments, which do not have a
> timestamp in a XLOG_BACKUP_END record.

I don't understand what "compatibility with WAL segments" could mean?
And how are WAL segments related to "XLOG_BACKUP_END record", except as
to how every WAL record is related? Are you thinking about the switch
records?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2018-07-10 02:15:39 Re: Usage of epoch in txid_current
Previous Message Noah Misch 2018-07-10 01:43:08 Extension relocation vs. schema qualification