From: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Fix corner-case bug in tracking of latest removed WAL segment du |
Date: | 2010-11-01 08:16:04 |
Message-ID: | [email protected] |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Fix corner-case bug in tracking of latest removed WAL segment during
streaming replication. We used log/seg 0/0 to indicate that no WAL segments
have been removed since startup, but 0/0 is a valid value for the very first
WAL segment after initdb. To make that disambiguous, store
(latest removed WAL segment + 1) in the global variable.
Per report from Matt Chesler, also reproduced by Greg Smith.
Branch
------
master
Modified Files
--------------
src/backend/access/transam/xlog.c | 9 ++++++---
src/backend/replication/walsender.c | 2 +-
2 files changed, 7 insertions(+), 4 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-11-01 17:56:11 | pgsql: Avoid using a local FunctionCallInfoData struct in ExecMakeFunct |
Previous Message | Tom Lane | 2010-10-31 15:43:51 | pgsql: Revert removal of trigger flag from plperl function hash key. |