From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> |
Cc: | "Nicolas Barbier" <nicolas(dot)barbier(at)gmail(dot)com>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>, "Bruce Momjian" <bruce(at)momjian(dot)us>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units. |
Date: | 2011-01-27 21:37:47 |
Message-ID: | 4D41914B0200002500039EE2@gw.wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from Kevin Grittner's message of jue ene 27 13:22:12
-0300 2011:
>> Bruce Momjian <bruce(at)momjian(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2011-01-27 21:39:55 | Re: REVIEW: PL/Python table functions |
Previous Message | Jan Urbański | 2011-01-27 21:33:01 | Re: pl/python SPI in subtransactions |