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

From Hannu Krosing
Subject Re: [PATCH] Cleanup of GUC units code
Date
Msg-id 1220480804.7603.17.camel@huvostro
Whole thread Raw
In response to Re: [PATCH] Cleanup of GUC units code  (Joshua Drake <jd@commandprompt.com>)
Responses Re: [PATCH] Cleanup of GUC units code
Re: [PATCH] Cleanup of GUC units code
Re: [PATCH] Cleanup of GUC units code
List pgsql-hackers
On Wed, 2008-09-03 at 11:45 -0700, Joshua Drake wrote:
> On Wed, 3 Sep 2008 19:36:19 +0100
> Greg Stark <greg.stark@enterprisedb.com> wrote:
> 
> > Sure if people want to do it the right way more power to them. What  
> > you're talking about is punishing people when they don't live up to  
> > your standards.
> 
> I think I will defer to Andrew and Alvaro's opinion on the matter.

So Andrews opinion was that Mb (meaning Mbit) is different from MB (for
megabyte) and that if someone thinks that we define shared buffers in
megabits can get confused and order wrong kind of network card ?

I can understand Alvaros stance more readily - if we have irrational
constraints on what can go into conf file, and people wont listen to
reason, then build better tools for helping people to compli to these
irrational demands. It has the added benefit of helping to catch reall
conf file errors.

I did not realize earlier that KB vs kb vs kB vs Kb is a religious
issue .

I mean, there is no known written standard, which says that Mb is
megabit, not megabyte or that you can (or can't) write kilo as K, but
some people just believe that kB is "the Way" and allowing people to
write kilobytes as KB or kb is evil and should be punished.

To me this sounds stupid, but I understand that this is a thing that
can't be argued logically and I have better things to do than changing
peoples irrational beliefs.

Sorry.

---------------
Hannu




pgsql-hackers by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: IN vs EXISTS equivalence
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] In case module has wrong magic, report exact problem