pgsql: Fix incorrect archive truncation point calculation in the %r - Mailing list pgsql-committers

From heikki@postgresql.org (Heikki Linnakangas)
Subject pgsql: Fix incorrect archive truncation point calculation in the %r
Date
Msg-id 20080509142809.0AD2B7559EA@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix incorrect archive truncation point calculation in the %r recovery_command
parameter. This fixes bug 4137 reported by Wojciech Strzalka, where a WAL
file is deleted too early when starting the recovery of a warm standby server.

Also add a sanity check in pg_standby so that it will refuse to delete anything
earlier than the file being restored, and improve the debug message in case
nothing is deleted.

Simon Riggs. Backpatch to 8.3, which is where %r was introduced.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
    pgsql/contrib/pg_standby:
        pg_standby.c (r1.10 -> r1.10.2.1)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_standby/pg_standby.c?r1=1.10&r2=1.10.2.1)
    pgsql/src/backend/access/transam:
        xlog.c (r1.292.2.1 -> r1.292.2.2)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.292.2.1&r2=1.292.2.2)

pgsql-committers by date:

Previous
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Fix incorrect archive truncation point calculation in the %r
Next
From: Tom Lane
Date:
Subject: Re: pgsql: Have numeric 0 ^ 4.3 return 1, rather than an error, and have 0 ^