| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Streaming replication and pg_xlogfile_name() |
| Date: | 2010-02-23 22:56:05 |
| Message-ID: | 1266965765.3752.4735.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2010-02-23 23:04:32 | Re: opportunistic tuple freezing |
| Previous Message | Bruce Momjian | 2010-02-23 22:49:41 | Re: opportunistic tuple freezing |