Skip site navigation (1) Skip section navigation (2)

Re: Streaming replication and pg_xlogfile_name()

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-25 16:34:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Thu, Feb 25, 2010 at 11:57 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Tue, Feb 23, 2010 at 4:08 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>>> 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.
> Hmm. How about using lastPageTLI instead of curFileTLI? lastPageTLI
> would always represent the TLI of the current record.

I attached the revised patch which uses lastPageTLI instead of curFileTLI
as the timeline of the last applied record.


Fujii Masao
NTT Open Source Software Center

Attachment: extend_format_of_recovery_info_funcs_v2.patch
Description: text/x-diff (12.9 KB)

In response to


pgsql-hackers by date

Next:From: Bruce MomjianDate: 2010-02-25 16:37:23
Subject: Re: pg_stop_backup does not complete
Previous:From: Dominik SanderDate: 2010-02-25 15:52:32
Subject: Boolean partition constraint behaving strangely

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group