| From: | Gregory Smith <gregsmithpgsql(at)gmail(dot)com> |
|---|---|
| To: | David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: rounding up time value less than its unit. |
| Date: | 2014-09-26 19:03:34 |
| Message-ID: | 5425B886.6000500@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/26/14, 2:34 PM, David Johnston wrote:
>
> I don't get where we "need" to do anything else besides that...the
> whole "actual min values" comment is unclear to me.
If you look at pg_settings, there is a minimum value exposed there as
min_val. For some of these parameters, that number would normally be
1. But since we have decided that 0 is a special flag value, min_val is
0 instead.
There are others where min_val is -1 for the same reason, where
functionally the minimum is really 0. Some of us would like to see
min_val reflect the useful minimum, period, and move all these special
case ones out of there. That is a multi-year battle to engage in
though, and there's little real value to the user community coming out
of it relative to that work scope.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-09-26 19:22:53 | Re: proposal: rounding up time value less than its unit. |
| Previous Message | Robert Haas | 2014-09-26 18:57:12 | Re: Replication identifiers, take 3 |