summaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuild.c
diff options
context:
space:
mode:
authorDavid Rowley <drowley@postgresql.org>2021-07-09 16:29:02 +1200
committerDavid Rowley <drowley@postgresql.org>2021-07-09 16:29:02 +1200
commit56ff8b29919f75a078969766393b9e20871a75c8 (patch)
tree9dd5ca154676ea3f20688f77195755b4e712b3c4 /src/backend/access/gist/gistbuild.c
parent55fe609387685de1c754332e260b2d0e17d257dc (diff)
downloadpostgresql-56ff8b29919f75a078969766393b9e20871a75c8.tar.gz
Use a lookup table for units in pg_size_pretty and pg_size_bytes
We've grown 2 versions of pg_size_pretty over the years, one for BIGINT and one for NUMERIC. Both should output the same, but keeping them in sync is harder than needed due to neither function sharing a source of truth about which units to use and how to transition to the next largest unit. Here we add a static array which defines the units that we recognize and have both pg_size_pretty and pg_size_pretty_numeric use it. This will make adding any units in the future a very simple task. The table contains all information required to allow us to also modify pg_size_bytes to use the lookup table, so adjust that too. There are no behavioral changes here. Author: David Rowley Reviewed-by: Dean Rasheed, Tom Lane, David Christensen Discussion: https://postgr.es/m/CAApHDvru1F7qsEVL-iOHeezJ+5WVxXnyD_Jo9nht+Eh85ekK-Q@mail.gmail.com
Diffstat (limited to 'src/backend/access/gist/gistbuild.c')
0 files changed, 0 insertions, 0 deletions