Postgres Pro
Downloads
Home   >   mailing lists

Re: custom function for converting human readable sizes to bytes - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: custom function for converting human readable sizes to bytes
Date
Msg-id CADkLM=fSCYg0UAYxx3pZC5zrkYJr5he1NcjHPnjrheSP+Dz42Q@mail.gmail.com
Whole thread Raw
In response to Re: custom function for converting human readable sizes to bytes  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: custom function for converting human readable sizes to bytes  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Tree view
On Sun, Nov 22, 2015 at 11:24 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:


2015-11-22 23:54 GMT+01:00 Corey Huinker <corey.huinker@gmail.com>:

What about pg_size_unpretty()?

I was going to suggest pg_size_ugly(), but unpretty does emphasize the inverse (rather than opposite) nature of the function.

"unpretty", "ugly" aren't good names

maybe pg_size_bytes or different approach

we can introduce data type - bytesize - default input/output is human readable text - and conversion to bigint is implicit

Some like

select .. where pg_table_size(oid) > bytesize '3.5GB'

and instead pg_size_pretty(pg_table_size(oid)) we can write pg_table_size(oid)::bytesize

Regards

Pavel

+1 to both pg_size_bytes() and ::bytesize. Both contribute to making the statements more self-documenting.

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: SPI and transactions
Next
From: Dean Rasheed
Date:
Subject: Re: onlyvalue aggregate (was: First Aggregate Funtion?)