Horton

Thread

  1. Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Peter Eisentraut <peter_e@gmx.net> — 2011-01-26T21:10:40Z

    We use small "k" in postgresql.conf, so pg_test_fsync should use the
same.  Using "kB" would be more accurate in any case.

  2. Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Bruce Momjian <bruce@momjian.us> — 2011-01-26T21:21:31Z

    Peter Eisentraut wrote:
> We use small "k" in postgresql.conf, so pg_test_fsync should use the
> same.  Using "kB" would be more accurate in any case.

OK, done with the attached applied patch.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

  3. Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Bruce Momjian <bruce@momjian.us> — 2011-01-27T00:06:41Z

    Bruce Momjian wrote:
> Peter Eisentraut wrote:
> > We use small "k" in postgresql.conf, so pg_test_fsync should use the
> > same.  Using "kB" would be more accurate in any case.
> 
> OK, done with the attached applied patch.

FYI, I had used 'k' because this page suggests that k is 1000 and K is
1024, at least by the JEDEC memory standards:

	http://en.wikipedia.org/wiki/Kilo

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

  4. Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Nicolas Barbier <nicolas.barbier@gmail.com> — 2011-01-27T10:09:41Z

    2011/1/27 Bruce Momjian <bruce@momjian.us>:

> Bruce Momjian wrote:
>
>> Peter Eisentraut wrote:
>>
>>> We use small "k" in postgresql.conf, so pg_test_fsync should use the
>>> same.  Using "kB" would be more accurate in any case.
>>
>> OK, done with the attached applied patch.
>
> FYI, I had used 'k' because this page suggests that k is 1000 and K is
> 1024, at least by the JEDEC memory standards:
>
>        http://en.wikipedia.org/wiki/Kilo

I can't find any reference to that on this page? The following does indeed say:

<URL:http://en.wikipedia.org/wiki/JEDEC_memory_standards>

<quote>
kilo (K): A multiplier equal to 1,024 [..] The specification notes
that these prefixes are included in the document only to reflect
common usage. It refers to the IEEE/ASTM SI 10-1997 standard as
stating, that "this practice frequently leads to confusion and is
deprecated".
</quote>

If you want to make the difference explicit, consider using "KiB"
(1024, note the extra "i") vs. "kB" (1000); although doing so is
probably not consistent with any other uses in PostgreSQL.

<URL:http://en.wikipedia.org/wiki/Kibibyte>

<quote>
The unit symbol for the kibibyte is KiB. The unit was established by
the International Electrotechnical Commission (IEC) in 1999 and has
been accepted for use by all major standards organizations.
</quote>

Nicolas

  5. Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Bruce Momjian <bruce@momjian.us> — 2011-01-27T15:53:23Z

    Nicolas Barbier wrote:
> 2011/1/27 Bruce Momjian <bruce@momjian.us>:
> 
> > Bruce Momjian wrote:
> >
> >> Peter Eisentraut wrote:
> >>
> >>> We use small "k" in postgresql.conf, so pg_test_fsync should use the
> >>> same. ?Using "kB" would be more accurate in any case.
> >>
> >> OK, done with the attached applied patch.
> >
> > FYI, I had used 'k' because this page suggests that k is 1000 and K is
> > 1024, at least by the JEDEC memory standards:
> >
> > ? ? ? ?http://en.wikipedia.org/wiki/Kilo
> 
> I can't find any reference to that on this page? The following does indeed say:

Sorry, I posed the wrong URL;  it should have been:

	http://en.wikipedia.org/wiki/Bytes#Unit_symbol

You can see the chart on the right.  However, I agree 'kB' is the best.

---------------------------------------------------------------------------

> <URL:http://en.wikipedia.org/wiki/JEDEC_memory_standards>
> 
> <quote>
> kilo (K): A multiplier equal to 1,024 [..] The specification notes
> that these prefixes are included in the document only to reflect
> common usage. It refers to the IEEE/ASTM SI 10-1997 standard as
> stating, that "this practice frequently leads to confusion and is
> deprecated".
> </quote>
> 
> If you want to make the difference explicit, consider using "KiB"
> (1024, note the extra "i") vs. "kB" (1000); although doing so is
> probably not consistent with any other uses in PostgreSQL.
> 
> <URL:http://en.wikipedia.org/wiki/Kibibyte>
> 
> <quote>
> The unit symbol for the kibibyte is KiB. The unit was established by
> the International Electrotechnical Commission (IEC) in 1999 and has
> been accepted for use by all major standards organizations.
> </quote>
> 
> Nicolas

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

  6. Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Kevin Grittner <kevin.grittner@wicourts.gov> — 2011-01-27T16:22:12Z

    Bruce Momjian <bruce@momjian.us> wrote:
 
> http://en.wikipedia.org/wiki/Bytes#Unit_symbol
> 
> You can see the chart on the right.
 
According to which, the JEDEC standard requires KB and the IEC
standard requires KiB.  What standard led us to use kB instead?  It
seems to generally mean 1000 instead of 1024.
 
> However, I agree 'kB' is the best.
 
Why?
 
-Kevin

  7. Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Bruce Momjian <bruce@momjian.us> — 2011-01-27T16:33:55Z

    Kevin Grittner wrote:
> Bruce Momjian <bruce@momjian.us> wrote:
>  
> > http://en.wikipedia.org/wiki/Bytes#Unit_symbol
> > 
> > You can see the chart on the right.
>  
> According to which, the JEDEC standard requires KB and the IEC
> standard requires KiB.  What standard led us to use kB instead?  It
> seems to generally mean 1000 instead of 1024.
	
I assume Peter did lots of research when he added 'kB' to
postgresql.conf.

> > However, I agree 'kB' is the best.
>  
> Why?

No idea.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

  8. Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Alvaro Herrera <alvherre@commandprompt.com> — 2011-01-27T21:24:18Z

    Excerpts from Kevin Grittner's message of jue ene 27 13:22:12 -0300 2011:
> Bruce Momjian <bruce@momjian.us> wrote:
>  
> > http://en.wikipedia.org/wiki/Bytes#Unit_symbol
> > 
> > You can see the chart on the right.
>  
> According to which, the JEDEC standard requires KB and the IEC
> standard requires KiB.  What standard led us to use kB instead?  It
> seems to generally mean 1000 instead of 1024.

http://en.wikipedia.org/wiki/International_System_of_Units#Writing_unit_symbols_and_the_values_of_quantities

-- 
Álvaro Herrera <alvherre@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

  9. Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.

    Kevin Grittner <kevin.grittner@wicourts.gov> — 2011-01-27T21:37:47Z

    Alvaro Herrera <alvherre@commandprompt.com> wrote:
> Excerpts from Kevin Grittner's message of jue ene 27 13:22:12
-0300 2011:
>> Bruce Momjian <bruce@momjian.us> wrote:
>>  
>> > http://en.wikipedia.org/wiki/Bytes#Unit_symbol
>> > 
>> > You can see the chart on the right.
>>  
>> According to which, the JEDEC standard requires KB and the IEC
>> standard requires KiB.  What standard led us to use kB instead? 
>> It seems to generally mean 1000 instead of 1024.
> 
>
http://en.wikipedia.org/wiki/International_System_of_Units#Writing_unit_symbols_and_the_values_of_quantities
 
That seems to agree with the other page that k means 10^3, not 2^10
-- or am I missing something?  We are treating it as 2^10 in our
GUCs, aren't we?
 
-Kevin