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 ------ REL8_4_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/73af46e82c501ec9122fd27c39c709f1d6fecc17 Modified Files -------------- src/backend/utils/misc/guc.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
