From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Tomonari Katsumata <katsumata(dot)tomonari(at)po(dot)ntts(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: proposal: rounding up time value less than its unit. |
Date: | 2014-08-21 20:01:31 |
Message-ID: | 53F6501B.3090201@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 8/21/14 11:16 AM, Tom Lane wrote:
> Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> writes:
>> The patch also rounds a zero up to one. A naked zero with no unit is not
>> affected, but e.g if you have "log_rotation_age=0s", it will not disable
>> the feature as you might expect, but set it to 1 minute. Should we do
>> something about that?
>
> That sounds like a dealbreaker to me. There are enough places where zero
> has special meaning that we should not *ever* change zero to non-zero
> silently.
I don't think I like this idea anyway. If something has units of an
hour and the user (perhaps misunderstanding the setting) sets it to one
second, then we shouldn't silently change that to one hour.
If there is a problem with rounding it to zero, then we should perhaps
raise an error. (And stop treating zero specially. It's a terrible idea.)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-08-21 20:01:34 | Re: run xmllint during build (was Re: need xmllint on borka) |
Previous Message | Tom Lane | 2014-08-21 20:00:01 | Re: run xmllint during build (was Re: need xmllint on borka) |