summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2021-07-09 18:56:00 +1200
committerDavid Rowley <drowley@postgresql.org>2021-07-09 18:56:00 +1200
commitca2e4472ba7b6e5e8cd8955eacffb90e4d88d085 (patch)
tree01f523c2e5b3b84896f632ad2f7a042dfa37d715 /src/backend/access/gist/gistbuild.c
parent0f80b47d24b470babd61f2d9927d1956075f771d (diff)
downloadpostgresql-ca2e4472ba7b6e5e8cd8955eacffb90e4d88d085.tar.gz
Teach pg_size_pretty and pg_size_bytes about petabytes
There was talk about adding units all the way up to yottabytes but it seems quite far-fetched that anyone would need those. Since such large units are not exactly commonplace, it seems unlikely that having pg_size_pretty outputting unit any larger than petabytes would actually be helpful to anyone. Since petabytes are on the horizon, let's just add those only. Maybe one day we'll get to add additional units, but it will likely be a while before we'll need to think beyond petabytes in regards to the size of a database. Author: David Christensen Discussion: https://postgr.es/m/CAOxo6XKmHc_WZip-x5QwaOqFEiCq_SVD0B7sbTZQk+qqcn2qaw@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions