On Wed, Feb 24, 2010 at 7:56 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Thu, 2010-01-28 at 10:28 +0200, Heikki Linnakangas wrote:
>> Fujii Masao wrote:
>> > In relation to the functions added recently, I found an annoying problem;
>> > pg_xlogfile_name(pg_last_xlog_receive/replay_location()) might report the
>> > wrong name because pg_xlogfile_name() always uses the current timeline,
>> > and a backend doesn't know the actual timeline related to the location
>> > which pg_last_xlog_receive/replay_location() reports. Even if a backend
>> > knows that, pg_xlogfile_name() would be unable to determine which timeline
>> > should be used.
>>
>> Hmm, I'm not sure what the use case for this is
>
> Agreed. What is the use case for this?
Since the current behavior would annoy many users (e.g., [*1]),
I proposed to change it.
[*1]
http://archives.postgresql.org/pgsql-hackers/2010-02/msg02014.php
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
