Quick Links

pgsql: Fix calculation of how many segments to retain for wal_keep_segm

From:	Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi>
To:	pgsql-committers(at)postgresql(dot)org
Subject:	pgsql: Fix calculation of how many segments to retain for wal_keep_segm
Date:	2013-04-08 13:30:22
Message-ID:	E1UPC9O-0001tc-3o@gemulon.postgresql.org
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-committers

Fix calculation of how many segments to retain for wal_keep_segments.

KeepLogSeg function was broken when we switched to use a 64-bit int for the
segment number.

Per report from Jeff Janes.

Branch
------
master

Modified Files
--------------
src/backend/access/transam/xlog.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)

	From	Date	Subject
Next Message	Tom Lane	2013-04-08 14:29:20	Re: pgsql: Avoid tricky race condition recording XLOG_HINT
Previous Message	Simon Riggs	2013-04-08 08:14:43	pgsql: Skip extraneous locking in XLogCheckBuffer().