| 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:04:39 |
| Message-ID: | 20100219010439.E94307541C5@cvs.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| 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_4_STABLE
Modified Files:
--------------
pgsql/src/backend/access/transam:
xlog.c (r1.345.2.6 -> r1.345.2.7)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/backend/access/transam/xlog.c?r1=1.345.2.6&r2=1.345.2.7)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Takahiro Itagaki | 2010-02-19 01:06:51 | pgsql: Fix STOP WAL LOCATION in backup history files no to return the |
| Previous Message | Takahiro Itagaki | 2010-02-19 01:04:03 | pgsql: Fix STOP WAL LOCATION in backup history files no to return the |