Re: effective_cache_size vs units

On Tue, 2006-12-19 at 16:47 -0500, Bruce Momjian wrote:
> Joshua D. Drake wrote:
> > On Tue, 2006-12-19 at 10:01 +0100, Peter Eisentraut wrote:
> > > Magnus Hagander wrote:
> > > > Is it possible to add an error hint to the message? Along the line of
> > > > "HINT: Did you perhaps get your casing wrong" (with better wording,
> > > > of course).
> > >
> > > Or how about we just make everything case-insensitive -- but
> > > case-preserving! -- on Windows only?
> >
> > Or we could simply add a helpful line to the postgresql.conf.
>
> Looking at the documentation I see:
>
> (possibly different) unit can also be specified explicitly. Valid
> memory units are <literal>kB</literal> (kilobytes),
> <literal>MB</literal> (megabytes), and <literal>GB</literal>
> (gigabytes); valid time units are <literal>ms</literal>
> (milliseconds), <literal>s</literal> (seconds),
> <literal>min</literal> (minutes), <literal>h</literal> (hours),
> and <literal>d</literal> (days). Note that the multiplier for
> memory units is 1024, not 1000.
>
> The only value to being case-sensitive in this area is to allow
> upper/lower case with different meanings, but I don't see us using that,
> so why do we bother caring about the case?

Because it is technically correct :).

Sincerely,

Joshua D. Drake

>
--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/

Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate