pgsql: Fix incorrect archive truncation point calculation in the %r

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix incorrect archive truncation point calculation in the %r
Date: 2008-05-09 14:28:09
Message-ID: 20080509142809.0AD2B7559EA@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2008-05-09 14:37:07 Re: pgsql: Have numeric 0 ^ 4.3 return 1, rather than an error, and have 0 ^
Previous Message Heikki Linnakangas 2008-05-09 14:27:48 pgsql: Fix incorrect archive truncation point calculation in the %r