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.
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Bruce Momjian||Date: 2010-02-25 16:37:23|
|Subject: Re: pg_stop_backup does not complete|
|Previous:||From: Dominik Sander||Date: 2010-02-25 15:52:32|
|Subject: Boolean partition constraint behaving strangely|