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

Re: pgsql: Correctly initialise shared recoveryLastRecPtr in recovery.

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Correctly initialise shared recoveryLastRecPtr in recovery.
Date: 2012-01-16 01:44:14
Message-ID: CAHGQGwHchuKzAUu2OKy1asRTV5_oDCFvnf4OLeJ9mgvGTs1NEg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Fri, Jan 13, 2012 at 10:05 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> Correctly initialise shared recoveryLastRecPtr in recovery.
> Previously we used ReadRecPtr rather than EndRecPtr, which was
> not a serious error but caused pg_stat_replication to report
> incorrect replay_location until at least one WAL record is replayed.

Thanks for the commit!

This needs to be backported to 9.1 and 9.0 because they also have
the same problem.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

pgsql-hackers by date

Next:From: Simon RiggsDate: 2012-01-16 01:52:35
Subject: Re: archive_keepalive_command
Previous:From: Greg SmithDate: 2012-01-16 01:03:16
Subject: Re: pgstat documentation tables

pgsql-committers by date

Next:From: Robert HaasDate: 2012-01-16 14:53:13
Subject: pgsql: Prevent adding relations to a concurrently dropped schema.
Previous:From: Andrew DunstanDate: 2012-01-15 21:21:53
Subject: Re: [COMMITTERS] pgsql: Fix breakage from earlier plperl fix.

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