| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Corey Huinker <corey(dot)huinker(at)gmail(dot)com> |
| Cc: | Guillaume Lelarge <guillaume(at)lelarge(dot)info>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Subject: | Re: custom function for converting human readable sizes to bytes |
| Date: | 2015-11-23 04:24:49 |
| Message-ID: | CAFj8pRAxOLJfoOcDx1JeHo_TgaYnwMoRm6iqB-Q6-5MGCzbB8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2015-11-22 23:54 GMT+01:00 Corey Huinker <corey(dot)huinker(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Praveen M | 2015-11-23 05:27:11 | Identify user requested queries |
| Previous Message | Andreas Karlsson | 2015-11-23 03:29:13 | Re: [PATCH] Reload SSL certificates on SIGHUP |