MIME-Version: 1.0
References: <19456-b16ffd2798ae6fd5@postgresql.org>
In-Reply-To: <19456-b16ffd2798ae6fd5@postgresql.org>
From: "David G. Johnston" <david.g.johnston@gmail.com>
Date: Wed, 15 Apr 2026 08:19:02 -0700
Message-ID: <CAKFQuwa+ax2T6V1+FRf2CriNJVRKk-Md2eWYWRiGXxMompTRhg@mail.gmail.com>
Subject: Re: BUG #19456: # Unit-Labeling Issue: `pg_size_pretty()` Incorrectly
 Labels Binary Units as Decimal Units
To: gautamkumar2764@gmail.com, pgsql-bugs@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000919e06064f813e9b"
Archived-At: <https://www.postgresql.org/message-id/CAKFQuwa%2Bax2T6V1%2BFRf2CriNJVRKk-Md2eWYWRiGXxMompTRhg%40mail.gmail.com>
Precedence: bulk

--000000000000919e06064f813e9b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, Apr 15, 2026 at 7:48=E2=80=AFAM PG Bug reporting form <
noreply@postgresql.org> wrote:

> The following bug has been logged on the website:
>
> Bug reference:      19456
> Logged by:          GAUTAM KUMAR
> Email address:      gautamkumar2764@gmail.com
> PostgreSQL version: 16.8
> Operating system:   LINUX
> Description:
>
> The function appears to calculate sizes using binary (base-2) division
>

You don't need to infer this, you can just read the documentation.

"Converts a size in bytes into a more easily human-readable format with
size units (bytes, kB, MB, GB, TB, or PB as appropriate). Note that the
units are powers of 2 rather than powers of 10, so 1kB is 1024 bytes, 1MB
is 10242 =3D 1048576 bytes, and so on."

https://www.postgresql.org/docs/current/functions-admin.html#FUNCTIONS-ADMI=
N-DBOBJECT

Which means it is not a bug.  And it's not the kind of behavior we are
going to change on people.

Maybe go write and submit a pg_size_iso(byte_count [, basis 2|10 default
10]) function.  I agree this is a gap that could be addressed.

I'd probably drop the pg_ prefix as well - that always just seemed odd to
me.  We have plenty of functions that are non-standard that we don't prefix
like this.

David J.

--000000000000919e06064f813e9b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:arial,helvetica,sans-serif"><span style=3D"font-family:Arial,Helve=
tica,sans-serif">On Wed, Apr 15, 2026 at 7:48=E2=80=AFAM PG Bug reporting f=
orm &lt;<a href=3D"mailto:noreply@postgresql.org">noreply@postgresql.org</a=
>&gt; wrote:</span></div></div><div class=3D"gmail_quote gmail_quote_contai=
ner"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">The following bug ha=
s been logged on the website:<br>
<br>
Bug reference:=C2=A0 =C2=A0 =C2=A0 19456<br>
Logged by:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 GAUTAM KUMAR<br>
Email address:=C2=A0 =C2=A0 =C2=A0 <a href=3D"mailto:gautamkumar2764@gmail.=
com" target=3D"_blank">gautamkumar2764@gmail.com</a><br>
PostgreSQL version: 16.8<br>
Operating system:=C2=A0 =C2=A0LINUX<br>
Description:=C2=A0 =C2=A0 =C2=A0 =C2=A0 <br><br>
The function appears to calculate sizes using binary (base-2) division<br><=
/blockquote><div><br></div><div class=3D"gmail_default" style=3D"font-famil=
y:arial,helvetica,sans-serif">You don&#39;t need to infer this, you can jus=
t read the documentation.</div><div class=3D"gmail_default" style=3D"font-f=
amily:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_default" st=
yle=3D"font-family:arial,helvetica,sans-serif">&quot;Converts a size in byt=
es into a more easily human-readable format with size units (bytes, kB, MB,=
 GB, TB, or PB as appropriate). Note that the units are powers of 2 rather =
than powers of 10, so 1kB is 1024 bytes, 1MB is 10242 =3D 1048576 bytes, an=
d so on.&quot;</div><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font=
-family:arial,helvetica,sans-serif"><a href=3D"https://www.postgresql.org/d=
ocs/current/functions-admin.html#FUNCTIONS-ADMIN-DBOBJECT">https://www.post=
gresql.org/docs/current/functions-admin.html#FUNCTIONS-ADMIN-DBOBJECT</a></=
div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-=
serif"><br></div><div class=3D"gmail_default" style=3D"font-family:arial,he=
lvetica,sans-serif">Which means it is not a bug.=C2=A0 And it&#39;s not the=
 kind of behavior we are going to change on people.</div><div class=3D"gmai=
l_default" style=3D"font-family:arial,helvetica,sans-serif"><br></div><div =
class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">Ma=
ybe go write and submit a pg_size_iso(byte_count [, basis 2|10 default 10])=
 function.=C2=A0 I agree this is a gap that could be addressed.</div><div c=
lass=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br=
></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,sa=
ns-serif">I&#39;d probably drop the pg_ prefix as well - that always just s=
eemed odd to me.=C2=A0 We have plenty of functions that are non-standard th=
at we don&#39;t prefix like this.</div><div class=3D"gmail_default" style=
=3D"font-family:arial,helvetica,sans-serif"><br></div><div class=3D"gmail_d=
efault" style=3D"font-family:arial,helvetica,sans-serif">David J.</div><div=
 class=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif">=
=C2=A0</div><div class=3D"gmail_default" style=3D"font-family:arial,helveti=
ca,sans-serif"><br></div></div></div>

--000000000000919e06064f813e9b--