Re: Streaming replication and pg_xlogfile_name()

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Streaming replication and pg_xlogfile_name()
Date: 2010-02-25 03:02:18
Message-ID: 3f0b79eb1002241902n3105f3c3i26afc4f3c1f36972@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 24, 2010 at 7:56 AM, Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gokulakannan Somasundaram 2010-02-25 07:19:05 Re: A thought on Index Organized Tables
Previous Message Fujii Masao 2010-02-25 02:57:35 Re: Streaming replication and pg_xlogfile_name()