Re: [BUGS] BUG #14244: wrong suffix for pg_size_pretty()

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Stark <stark(at)mit(dot)edu>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, thomas(dot)berger(at)1und1(dot)de, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [BUGS] BUG #14244: wrong suffix for pg_size_pretty()
Date: 2016-09-13 20:52:14
Message-ID: 70e98994-c7d5-6be5-9cc6-cf34eb556183@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 7/30/16 2:16 PM, Bruce Momjian wrote:
> The second patch does what Tom suggests above by outputting only "KB",
> and it supports "kB" for backward compatibility. What it doesn't do is
> to allow arbitrary case, which I think would be a step backward. The
> second patch actually does match the JEDEC standard, except for allowing
> "kB".

Btw., just to show that I'm not all crazy, the following programs also
display a small "k" for file sizes and download rates:

apt
curl
dnf
pip
yum
vagrant

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2016-09-13 20:52:22 Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()
Previous Message Keith Fiske 2016-09-13 20:50:50 Re: BUG #14322: Possible inconsistent behavior with timestamp_to_str()

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2016-09-13 20:56:28 Re: Logical Replication WIP
Previous Message Tom Lane 2016-09-13 20:49:09 Re: Inheriting PostgresNode object