| From: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Beena Emerson <memissemerson(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: Memory unit GUC range checks |
| Date: | 2018-05-16 17:17:38 |
| Message-ID: | 1550e1f3-3fbd-ed3a-5043-38d9d247afb4@iki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 16/05/18 16:35, Alexander Korotkov wrote:
> I also think it would be nice to show units in the valid range. I image
> that if I would see such message at the first time, then I would try to
> reverse-engineer units from input value representation in the error
> message. Displaying units in the valid range would be clarifying for me.
Totally agreed. Users shouldn't need to know whether the base unit for a
setting is bytes or kilobytes or megabytes. But that sounds like a
feature rather than a bug, so, not now.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2018-05-16 17:48:26 | Re: An out-of-date comment in nodeIndexonlyscan.c |
| Previous Message | Robert Haas | 2018-05-16 16:37:48 | Re: log_min_messages shows debug instead of debug2 |