Re: Streaming replication and pg_xlogfile_name()

From: "Erik Rijkers" <er(at)xs4all(dot)nl>
To: "Fujii Masao" <masao(dot)fujii(at)gmail(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-03-05 00:20:11
Message-ID: c74d7d127a23e41a50cc2f4b85dbde52.squirrel@webmail.xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, March 3, 2010 15:03, Fujii Masao wrote:
> On Tue, Mar 2, 2010 at 10:52 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>
> Here is the revised patch. I used new local variable instead of lastPageTLI
> to track the tli of last applied record. It is updated with the tli of the
> log page header when reading the page, and with the tli of the checkpoint
> record when replaying the checkpoint shutdown record that changes the tli.
> So pg_last_xlog_replay_location() can return the accurate tli of the last
> applied record.
>
> extend_format_of_recovery_info_funcs_v4.patch

looks good: on the standby, the initial xlog file_name immediately after startup is now
000000010000000000000001, as expected.

I'll do my further testing of HS/SR with this patch included.

thanks,

Erik Rijekrs

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2010-03-05 03:41:30 Re: Repetition of warning message while REVOKE
Previous Message Kevin Flanagan 2010-03-05 00:19:53 Visual Studio 2005, C-language function - avoiding hacks?