| From: | "Andrey V(dot) Lepikhov" <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | "g(dot)smolkin(at)postgrespro(dot)ru" <g(dot)smolkin(at)postgrespro(dot)ru> |
| Subject: | [PATCH] Timestamp for a XLOG_BACKUP_END WAL-record |
| Date: | 2018-07-10 01:41:32 |
| Message-ID: | [email protected] |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
I prepared a patch which adds a timestamp into a XLOG_BACKUP_END
WAL-record. This functionality is needed in practice when we have to
determine a 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.
--
Andrey Lepikhov
Postgres Professional:
https://postgrespro.com
The Russian Postgres Company
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-BACKUP_END-timestamp-addition.patch | text/x-patch | 2.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2018-07-10 01:43:08 | Extension relocation vs. schema qualification |
| Previous Message | Andres Freund | 2018-07-10 01:30:57 | Re: Usage of epoch in txid_current |