2015-11-22 23:54 GMT+01:00 Corey Huinker <corey.huin...@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
