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

Re: testing cvs HEAD - HS/SR - missing file

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Erik Rijkers <er(at)xs4all(dot)nl>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: testing cvs HEAD - HS/SR - missing file
Date: 2010-01-26 19:02:53
Message-ID: 3f0b79eb1001261102q7da2d79ase3646eb5fcc5e408@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Jan 27, 2010 at 2:19 AM, Erik Rijkers <er(at)xs4all(dot)nl> wrote:
> Now, when restoring a 700MB dump (made with a 9.0devel pg_dump + pg_restore) into the primary,
> errors like the following occur, on all three instances:
>
> FATAL:  could not open file "pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such
> file or directory

Thanks for the report!

This is the bug of SR :( I think that walsender wrongly treats the WAL-boundary.

> pgsql.sr_slave02/logfile:ERROR:  could not read xlog records: FATAL:  could not open file
> "pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such file or directory
> pgsql.sr_slavery/logfile:ERROR:  could not read xlog records: FATAL:  could not open file
> "pg_xlog/0000000100000001000000FF" (log file 1, segment 255): No such file or directory

Also the ReadRecord() or its surrounding functions seem to have treated
wrongly the WAL-boundary.

I'll fix those bugs after a night's sleep.

Regards,

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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2010-01-26 19:12:50
Subject: Re: unfathomable comment in psqlscan.l
Previous:From: Josh BerkusDate: 2010-01-26 19:01:12
Subject: Re: Dividing progress/debug information in pg_standby, and stat before copy

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