Re: pending patch: Re: Streaming replication and pg_xlogfile_name() - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: pending patch: Re: Streaming replication and pg_xlogfile_name()
Date
Msg-id 4BBB0C09.1050708@enterprisedb.com
Whole thread Raw
In response to Re: pending patch: Re: Streaming replication and pg_xlogfile_name()  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: pending patch: Re: Streaming replication and pg_xlogfile_name()
List pgsql-hackers
Fujii Masao wrote:
> On Fri, Apr 2, 2010 at 2:22 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> Can someone explain to me in plain language what problem this is
>> trying to fix?  I'm having trouble figuring it out.
> 
> The problem is that pg_xlogfile_name(pg_last_xlog_receive_location()) and
> pg_xlogfile_name(pg_last_xlog_replay_location()) might report an inaccurate
> WAL file name because currently pg_xlogfile_name() always uses the current
> timeline to calculate the WAL file name. For example, even though the last
> applied WAL file is 000000010000000000000002, the standby wrongly reports
> that 000000000000000000000002 has been applied last.

Should we throw an error in pg_xlogfile_name() if called during
recovery? It's not doing anything useful as it is.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Check compulsory parameters in recovery.conf in standby_mode, per
Next
From: Fujii Masao
Date:
Subject: Re: pending patch: Re: Streaming replication and pg_xlogfile_name()