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

Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Date: 2010-02-11 10:37:37
Message-ID: 1265884657.7341.1192.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-docspgsql-hackers
On Wed, 2010-02-10 at 09:32 +0200, Heikki Linnakangas wrote:
> Fujii Masao wrote:
> > As I pointed out previously, the standby might restore a partially-filled
> > WAL file that is being archived by the primary, and cause a FATAL error.
> > And this happened in my box when I was testing the SR.
> > 
> >   sby [20088] FATAL:  archive file "000000010000000000000087" has
> > wrong size: 14139392 instead of 16777216
> >   sby [20076] LOG:  startup process (PID 20088) exited with exit code 1
> >   sby [20076] LOG:  terminating any other active server processes
> >   act [18164] LOG:  received immediate shutdown request
> > 
> > If the startup process is in standby mode, I think that it should retry
> > starting replication instead of emitting an error when it finds a
> > partially-filled file in the archive. Then if the replication has been
> > terminated, it has only to restore the archived file again. Thought?
> 
> Hmm, so after running restore_command, check the file size and if it's
> too short, treat it the same as if restore_command returned non-zero?
> And it will be retried on the next iteration. Works for me, though OTOH
> it will then fail to complain about a genuinely WAL file that's
> truncated for some reason. I guess there's no way around that, even if
> you have a script as restore_command that does the file size check, it
> will have the same problem.

Are we trying to re-invent pg_standby here?

-- 
 Simon Riggs           www.2ndQuadrant.com


In response to

Responses

pgsql-docs by date

Next:From: Heikki LinnakangasDate: 2010-02-11 12:22:16
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Previous:From: Thom BrownDate: 2010-02-10 22:43:13
Subject: Confusing link in streaming replication section

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2010-02-11 11:03:08
Subject: Re: log_error_verbosity function display
Previous:From: Simon RiggsDate: 2010-02-11 10:34:56
Subject: Re: Parameter name standby_mode

pgsql-committers by date

Next:From: Andres FreundDate: 2010-02-11 11:04:07
Subject: Re: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while
Previous:From: Simon RiggsDate: 2010-02-11 10:10:32
Subject: Re: [COMMITTERS] pgsql: Remove old-style VACUUM FULL (which was known for a little while

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