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

pgsql: Fix STOP WAL LOCATION in backup history files no to return the

From: itagaki(at)postgresql(dot)org (Takahiro Itagaki)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix STOP WAL LOCATION in backup history files no to return the
Date: 2010-02-19 01:06:51
Message-ID: 20100219010651.BF1227541C5@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Fix STOP WAL LOCATION in backup history files no to return the next
segment of XLOG_BACKUP_END record even if the the record is placed
at a segment boundary. Furthermore the previous implementation could
return nonexistent segment file name when the boundary is in segments
that has "FE" suffix; We never use segments with "FF" suffix.

Backpatch to 8.0, where hot backup was introduced.

Reported by Fujii Masao.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
    pgsql/src/backend/access/transam:
        xlog.c (r1.292.2.9 -> r1.292.2.10)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.292.2.9&r2=1.292.2.10)

pgsql-committers by date

Next:From: Takahiro ItagakiDate: 2010-02-19 01:07:57
Subject: pgsql: Fix STOP WAL LOCATION in backup history files no to return the
Previous:From: Takahiro ItagakiDate: 2010-02-19 01:04:39
Subject: pgsql: Fix STOP WAL LOCATION in backup history files no to return the

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