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

From Simon Riggs
Subject Re: Streaming replication and pg_xlogfile_name()
Date
Msg-id 1266965765.3752.4735.camel@ebony
Whole thread Raw
In response to Re: Streaming replication and pg_xlogfile_name()  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Streaming replication and pg_xlogfile_name()
List pgsql-hackers
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?

-- Simon Riggs           www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: opportunistic tuple freezing
Next
From: Jeff Davis
Date:
Subject: Re: opportunistic tuple freezing