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

pgsql: Limit values of archive_timeout, post_auth_delay,auth_delay.mil

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Limit values of archive_timeout, post_auth_delay,auth_delay.mil
Date: 2012-11-18 22:16:04
Message-ID: E1TaD9o-0004mw-3e@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Limit values of archive_timeout, post_auth_delay, auth_delay.milliseconds.

The previous definitions of these GUC variables allowed them to range
up to INT_MAX, but in point of fact the underlying code would suffer
overflows or other errors with large values.  Reduce the maximum values
to something that won't misbehave.  There's no apparent value in working
harder than this, since very large delays aren't sensible for any of
these.  (Note: the risk with archive_timeout is that if we're late
checking the state, the timestamp difference it's being compared to
might overflow.  So we need some amount of slop; the choice of INT_MAX/2
is arbitrary.)

Per followup investigation of bug #7670.  Although this isn't a very
significant fix, might as well back-patch.

Branch
------
REL9_1_STABLE

Details
-------
http://git.postgresql.org/pg/commitdiff/fe838e5074149058a1101092d3a557e4b86b8ff2

Modified Files
--------------
contrib/auth_delay/auth_delay.c |    2 +-
src/backend/utils/misc/guc.c    |    4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2012-11-19 08:20:43
Subject: pgsql: Fix archive_cleanup_command.
Previous:From: Tom LaneDate: 2012-11-18 22:16:03
Subject: pgsql: Limit values of archive_timeout, post_auth_delay,auth_delay.mil

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