Sorry for the delay.
On Fri, Feb 26, 2010 at 6:26 AM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> With this patch the standby compiles, tests, installs OK.
> I wanted to check with you if the following is expected.
Thanks for the test and bug report!
> With standby (correctly) as follows :
> LOG: redo starts at 0/1000020
> LOG: consistent recovery state reached at 0/2000000
> LOG: database system is ready to accept read only connections
> This is OK.
> However, initially (even after the above 'ready' message)
> the timeline value as reported by
> is zero.
When we try to read the WAL record discontinuously (e.g., the REDO
starting record and the last applied record), the lastPageTLI is
always reset. If that record is not in the buffer, it's read from
the disk and the lastPageTLI is set to the right timeline. Otherwise,
the lastPageTLI remains at zero wrongly. This is the cause of the
problem that you reported.
I revised the patch so that the lastPageTLI is always set correctly.
Please try this new patch.
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center
In response to
pgsql-hackers by date
|Next:||From: Heikki Linnakangas||Date: 2010-03-02 07:11:50|
|Subject: Re: pg_stop_backup does not complete|
|Previous:||From: Nikhil Sontakke||Date: 2010-03-02 06:48:22|
|Subject: Re: plpgsql: numeric assignment to an integer variable errors out|