public inbox for [email protected]
help / color / mirror / Atom feedFrom: Randy Isbell <[email protected]>
To: [email protected]
Subject: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION
Date: Fri, 5 Dec 2008 14:41:16 GMT
Message-ID: <[email protected]> (raw)
The following bug has been logged online:
Bug reference: 4566
Logged by: Randy Isbell
Email address: [email protected]
PostgreSQL version: 8.3.4
Operating system: FreeBSD 6.2
Description: pg_stop_backup() reports incorrect STOP WAL LOCATION
Details:
An inconsistency exists between the segment name reported by
pg_stop_backup() and the actual WAL file name.
SELECT pg_start_backup('filename');
pg_start_backup
-----------------
10/FE1E2BAC
(1 row)
Later:
SELECT pg_stop_backup();
pg_stop_backup
----------------
10/FF000000
(1 row)
The resulting *.backup file:
START WAL LOCATION: 10/FE1E2BAC (file 0000000200000010000000FE)
STOP WAL LOCATION: 10/FF000000 (file 0000000200000010000000FF)
CHECKPOINT LOCATION: 10/FE1E2BAC
START TIME: 2008-11-09 01:15:06 CST
LABEL: /bck/db/sn200811090115.tar.gz
STOP TIME: 2008-11-09 01:15:48 CST
In my 8.3.4 instance, WAL file naming occurs as:
...
0000000100000003000000FD
0000000100000003000000FE
000000010000000400000000
000000010000000400000001
...
WAL files never end in 'FF'. This causes a problem when trying to collect
the ending WAL file for backup.
- r.
view thread (22+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: BUG #4566: pg_stop_backup() reports incorrect STOP WAL LOCATION
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox