From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Streaming replication and pg_xlogfile_name() |
Date: | 2010-02-23 07:08:44 |
Message-ID: | 4B837EFC.4010402@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Fujii Masao wrote:
> 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.
Yes.
> So it's not the TLI of the first record in the file, isn't it?
Hmm, or is it the TLI of the last record? Not sure. Anyway, if there's a
TLI switch in the current WAL file, curFileTLI doesn't always represent
the TLI of the current record.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2010-02-23 07:43:21 | Re: [COMMITTERS] Re: pgsql: Speed up CREATE DATABASE by deferring the fsyncs until after |
Previous Message | Bruce Momjian | 2010-02-23 06:59:15 | to_char("HH12") with intervals |