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 15:45:41
Message-ID: 3f0b79eb1002250745y6c4bac5dq2178f6b1df49b6e8@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 25, 2010 at 6:33 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> If we expose the timeline as part of an "xlog location", then we should
> do that everywhere as a change for 9.0.

Everywhere? You mean changing the format of the return value of all
the following functions?

- pg_start_backup()
- pg_stop_backup()
- pg_switch_xlog()
- pg_current_xlog_location()
- pg_current_xlog_insert_location()

> Clearly, "xlog location" has no
> meaning without the timeline anyway, so this seems like a necessary
> change not just a quick fix. It breaks compatibility, but since we're
> changing replication in 9.0 that shouldn't be a problem.

Umm... ISTM a large number of users would complain about that
change because of compatibility.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2010-02-25 15:49:52 Re: Odd CVS revision number
Previous Message Tom Lane 2010-02-25 15:37:59 Re: NaN/Inf fix for ECPG