Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset
Date
Msg-id 3f0b79eb1002241736h7804ded5pd58472cc54690871@mail.gmail.com
Whole thread Raw
In response to Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset  ("Erik Rijkers" <er@xs4all.nl>)
Responses Re: testing cvs HEAD - HS/SR - xlog timeline 0 pg_xlogfile_name_offset
List pgsql-hackers
On Thu, Feb 25, 2010 at 9:31 AM, Erik Rijkers <er@xs4all.nl> wrote:
> On Wed, February 24, 2010 20:40, Erik Rijkers wrote:
>>
>>
>>  pg_last_xlog_receive_location |      pg_xlogfile_name_offset
>> -------------------------------+-----------------------------------
>>  E2/C012AD90                   | (00000000000000E2000000C0,1224080)
>>  (1 row)
>>
>> These zero-timeline filenames look suspicious, no?
>
> Sorry, I've only now noticed that this issue is already on the v9.0 TODO for Streaming Replication:
>
> "pg_xlogfile_name(pg_last_xlog_receive/replay_location()) might report the wrong name. Because a
> backend cannot know the actual timeline which is related to the location.
> "
>
> http://archives.postgresql.org/message-id/3f0b79eb1001190135vd9f62f1sa7868abc1ea61d12@mail.gmail.com
>
> so, nevermind..

Yeah, since I thought that the current behavior that you reported
would annoy many users, I added it to the TODO list.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: pg_stop_backup does not complete
Next
From: Greg Smith
Date:
Subject: Re: pg_stop_backup does not complete