From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: custom function for converting human readable sizes to bytes |
Date: | 2015-11-22 20:11:48 |
Message-ID: | CAFj8pRAnRpzFX_WDtcZhjByxj+j0QxrtM2qQRQrFVUXyKahFmw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2015-11-22 18:30 GMT+01:00 Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>:
> On 11/21/15 12:49 AM, Pavel Stehule wrote:
>
>>
>> I propose inversion function to pg_size_pretty function - like
>> pg_human_size.
>>
>> Usage:
>>
>> SELECT * FROM pg_class
>> WHERE pg_table_size(oid) > pg_human_size('2GB');
>>
>
> I'm not a big fan of the name, but +1 on the general idea.
>
I am for any other good name
>
> Maybe pg_size_pretty(text)?
>
I understand to your idea, but it can be too strange - function and
inversion function share same name.
What about pg_size(text), pg_size(value bigint, unit text) ?
Regards
Pavel
> --
> Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
> Experts in Analytics, Data Architecture and PostgreSQL
> Data in Trouble? Get it in Treble! http://BlueTreble.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Marko Tiikkaja | 2015-11-22 20:16:18 | Re: custom function for converting human readable sizes to bytes |
Previous Message | Marko Tiikkaja | 2015-11-22 17:34:24 | Re: count_nulls(VARIADIC "any") |