From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming replication and pg_xlogfile_name() |
Date: | 2010-02-23 02:37:24 |
Message-ID: | 3f0b79eb1002221837n3495da88o794df644a89bdaa9@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 22, 2010 at 9:30 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Thinking about this again, I'm not sure this is a good idea. Using
> curFileTLI makes sense if you're going to call pg_xlogfile_name() and
> would expect it to return the filename of the file containing the WAL
> record being replayed. But in other contexts, it seems strange for
> pg_last_replay_timeline() to return the TLI of the first record in the
> file, rather than the actual record replayed.
Umm... though I might misunderstand your point, curFileTLI is the TLI
appearing in the name of WAL file. So it's not the TLI of the first
record in the file, isn't it?
Regards,
--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-02-23 02:54:22 | Re: Elementary dependency look-up |
Previous Message | Bruce Momjian | 2010-02-23 02:35:41 | Re: [PATCH] backend: compare word-at-a-time in bcTruelen |