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

Unnecessary limit on max_standby_streaming_delay

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Unnecessary limit on max_standby_streaming_delay
Date: 2010-12-17 11:57:48
Message-ID: AANLkTik_x=n=BfQAcds9DAyY5LQLVCQhXxNZ93N-UuwC@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
The limit on max_standby_streaming_delay is currently 35 minutes
(around) - or you have to set it to unlimited. This is because the GUC
is limited to MAX_INT/1000, unit milliseconds.

Is there a reason for the /1000, or is it just an oversight thinking
the unit was in seconds?

If we can get rid of the /1000, it would make the limit over three
weeks, which seems much more reasonable. Or if we made it a 64-bit
counter it would go away completely.

-- 
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

Responses

pgsql-hackers by date

Next:From: Greg SmithDate: 2010-12-17 12:18:07
Subject: Re: Unnecessary limit on max_standby_streaming_delay
Previous:From: Magnus HaganderDate: 2010-12-17 11:17:37
Subject: Re: Re: Proposed Windows-specific change: Enable crash dumps (like core files)

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