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

pgsql: Change the retry-loop in standby mode to also try restoring files

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Change the retry-loop in standby mode to also try restoring files
Date: 2010-03-30 16:23:57
Message-ID: 20100330162357.BF3C67541D0@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Change the retry-loop in standby mode to also try restoring files from
pg_xlog directory. This is essential for replaying WAL records that
were streamed from the master, after a standby server restart.

If a corrupt record is seen in a file restored from the archive or
streamed from the master, log it as a WARNING and keep retrying. If the
corruption is permanent, and not just a glitch in the whatever copies the
files to the archive or a network error not caught by CRC checks in TCP
for example, we will keep retrying and logging the WARNING indefinitely.
But that's better than shutting down completely, the standby is still
useful for running read-only queries. In PITR the recovery ends at such a
corrupt record, which is a bit questionable, but that's the behavior we
had in previous releases and we don't feel like chaning it now. It does
make sense for tools like pg_standby.

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.384 -> r1.385)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.384&r2=1.385)

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2010-03-30 16:28:28
Subject: Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL
Previous:From: Peter EisentrautDate: 2010-03-30 16:08:23
Subject: pgsql: Message tuning

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