In reality,sometimes something would be wrong if you hard-coding 1
minute as 60 seconds.
"The range of seconds is (00-60) instead of (00-59) to allow for the
periodic occurrence of leap seconds."
so,it's a bad habit including hard-coding 1 minute as 60 seconds.
On Thu, Oct 27, 2011 at 13:13, Heikki Linnakangas
> On 27.10.2011 15:57, Robert Young wrote:
>> But,I think insistence of hard-coding should be even worse than broken
>> And hard-coding should never be a good work ethics of a professional
> You're exaggerating. There's nothing wrong hard-coding things like number of
> seconds in a minute (60). While it's not as cast in stone as 60 seconds in a
> minute, I don't see anything wrong with hardcoding that "localhost" means
> the local host.
> BTW, do we have anything in place to stop any user on the same host to send
> bogus stat messages to the stats collector?
> Heikki Linnakangas
> EnterpriseDB http://www.enterprisedb.com
In response to
pgsql-bugs by date
|Next:||From: Justin||Date: 2011-10-27 13:46:17|
|Subject: BUG #6273: Install Error|
|Previous:||From: Heikki Linnakangas||Date: 2011-10-27 13:13:20|
|Subject: Re: Add statistics_collector_listen_addresses to fix hard-coding