Re: effective_cache_size vs units - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: effective_cache_size vs units
Date
Msg-id 20A73B60-41F0-4FAB-BF91-252F688E6449@decibel.org
Whole thread Raw
In response to Re: effective_cache_size vs units  ("Andrew Hammond" <andrew.george.hammond@gmail.com>)
List pgsql-hackers
You just proved the case for why the units shouldn't be case sensitive:

On Dec 30, 2006, at 6:36 PM, Andrew Hammond wrote:
> I agree. But perhaps the solution instead of failing is to throw a
> warning to the effect of "Not to be pedantic, but you said mb and
> millibits as a unit doesn't make sense in this context. Assuming you
> meant MB (MegaBits)." and then start up.

Do we really want people specifying effective_cache_size in *bits*,  
mega or not? I think no.

To reply to Peter's comment, yes, bits would be useful if we ever  
actually have any settings relating to network bandwidth. But that's  
a really big IF. IF we do eventually decide to add such a setting, I  
think it would make the most sense to spell out 'bits' in the unit.
--
Jim Nasby                                            jim@nasby.net
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)




pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: Re: Deadline-Based Vacuum Delay
Next
From: Jim Nasby
Date:
Subject: Re: TODO: Add a GUC to control whether BEGIN inside