Postgres Pro
Downloads
Home   >   mailing lists

Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units. - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.
Date
Msg-id 201101270006.p0R06fF24588@momjian.us
Whole thread Raw
In response to Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Re: In pg_test_fsync, use K(1024) rather than k(1000) for write size units.  (Nicolas Barbier <nicolas.barbier@gmail.com>)
List pgsql-hackers
Tree view 
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. +

pgsql-hackers by date:

Previous
From: Jan Urbański
Date:
Subject: Re: pl/python refactoring
Next
From: Tom Lane
Date:
Subject: Re: [NOVICE] systable_getnext_ordered