Re: [PATCH] Cleanup of GUC units code - Mailing list pgsql-hackers

From Marko Kreen
Subject Re: [PATCH] Cleanup of GUC units code
Date
Msg-id e51f66da0809020654g4773d443gbfef413ee4dcdf21@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Cleanup of GUC units code  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: [PATCH] Cleanup of GUC units code  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
On 9/2/08, Peter Eisentraut <peter_e@gmx.net> wrote:
> Gregory Stark wrote:
> > Peter Eisentraut <peter_e@gmx.net> writes:
> > > Marko Kreen wrote:
> > > > In the meantime, here is simple patch for case-insensivity.
> > > >
> > > You might be able to talk me into accepting various unambiguous, common
> > > alternative spellings of various units.  But for instance allowing MB
> and Mb to
> > > mean the same thing is insane.
> > >
> >
> > Because you think some user will be trying to specify their shared_buffers
> in
> > bits?
> >
>
>  My concern is that this information does not stay in the configuration
> files.  It will invariably leak out into whitepapers, presentations, product
> documentation, and before long there will be confusion about why you can't
> stuff N Mb over an N Mb connection.  I am not making this up.

Uh.  So you want force "proper" units in presentations at the price
of everyday admin operations?  Does not seem like a sensible tradeoff.

-- 
marko


pgsql-hackers by date:

Previous
From: "Marko Kreen"
Date:
Subject: Re: [PATCH] Cleanup of GUC units code
Next
From: Alvaro Herrera
Date:
Subject: Re: Out-of-tree compilation seems broken in HEAD (plpgsql)