From 6eb9c5a5657d1fe77b55cc261450f3538d35a94d Mon Sep 17 00:00:00 2001 From: Daniel Baumann Date: Sat, 4 May 2024 14:19:15 +0200 Subject: Adding upstream version 13.4. Signed-off-by: Daniel Baumann --- doc/src/sgml/html/backup-manifest-wal-ranges.html | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/src/sgml/html/backup-manifest-wal-ranges.html (limited to 'doc/src/sgml/html/backup-manifest-wal-ranges.html') diff --git a/doc/src/sgml/html/backup-manifest-wal-ranges.html b/doc/src/sgml/html/backup-manifest-wal-ranges.html new file mode 100644 index 0000000..79138fc --- /dev/null +++ b/doc/src/sgml/html/backup-manifest-wal-ranges.html @@ -0,0 +1,22 @@ + +72.3. Backup Manifest WAL Range Object
72.3. Backup Manifest WAL Range Object
Prev UpChapter 72. Backup Manifest FormatHome Next

72.3. Backup Manifest WAL Range Object

+ The object which describes a WAL range always has three keys: +

Timeline

+ The timeline for this range of WAL records, as an integer. +

Start-LSN

+ The LSN at which replay must begin on the indicated timeline in order to + make use of this backup. The LSN is stored in the format normally used + by PostgreSQL; that is, it is a string + consisting of two strings of hexadecimal characters, each with a length + of between 1 and 8, separated by a slash. +

End-LSN

+ The earliest LSN at which replay on the indicated timeline may end when + making use of this backup. This is stored in the same format as + Start-LSN. +

+ Ordinarily, there will be only a single WAL range. However, if a backup is + taken from a standby which switches timelines during the backup due to an + upstream promotion, it is possible for multiple ranges to be present, each + with a different timeline. There will never be multiple WAL ranges present + for the same timeline. +

Prev Up Next
72.2. Backup Manifest File Object Home Part VIII. Appendixes
\ No newline at end of file -- cgit v1.2.3