-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Fujii Masao wrote: > On Mon, Feb 1, 2010 at 7:33 PM, Rafael Martinez > <r.m.guerr...@usit.uio.no> wrote:
>> >> Any thoughts about this? Is this a bug or a 'feature'? > > This is not a bug. Since pg_start_backup() uses "%X/%X" (not "%08X/%08X") > as the format of WAL location, the length of the second number of the WAL > location could be less than 8. > > Instead of calculating the name of the backup history file for yourself, > how about using pg_xlogfile_name() or pg_xlogfile_name_offset()? Thanks for the answer. We have updated our code and started using pg_xlogfile_name() in our PITR script. Everything works perfect now. When we started using PITR with version 8.1, we didn't have these functions and that was the reason we were using the value returned by pg_start_backup() to find out the last WAL to keep after PITR was finnish. regards, - -- Rafael Martinez, <r.m.guerr...@usit.uio.no> Center for Information Technology Services University of Oslo, Norway PGP Public Key: http://folk.uio.no/rafael/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFLaUXLBhuKQurGihQRAqNpAKCLCc6MDhGONJi5fTgStFoC+PP6hgCdHqVC yDfsC1erRWxFJRCF305Bbg8= =Brbz -----END PGP SIGNATURE----- -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
