Fujii Masao wrote:
> On Mon, Jan 4, 2010 at 9:55 PM, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> > Heikki Linnakangas wrote:
> >> Here's is modified patch that adds a new backupStartPoint field to
> >> pg_control for that + some other minor editorialization.
> >
> > I've committed this now.
> 
> Thanks a lot!
> 
> src/backend/access/transam/xlog.c
> > else
> > {
> > 	XLogRecPtr	InvalidXLogRecPtr = {0, 0};
> > 	ControlFile->minRecoveryPoint = InvalidXLogRecPtr;
> > }
> 
> In my original patch, the above is for the problem discussed in
> http://archives.postgresql.org/pgsql-hackers/2009-12/msg02039.php
> 
> Since you've already fixed the problem, that code is useless.
> How about getting rid of that code?

Has this been addressed?

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

• Re: Backup history file should be replicated in Streaming Replication? at 2010-01-05 05:32:58 from Fujii Masao

Responses

• Re: Backup history file should be replicated in Streaming Replication? at 2010-02-08 01:01:40 from Fujii Masao

pgsql-hackers by date

Next:	From: Andres Freund	Date: 2010-02-06 16:32:43
	Subject: Re: Hot Standby and DROP DATABASE
Previous:	From: Bruce Momjian	Date: 2010-02-06 15:59:16
	Subject: Re: archive_timeout behavior for no activity