aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/arrayfuncs.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-11-17 11:20:53 +0900
committerMichael Paquier <michael@paquier.xyz>2023-11-17 11:20:53 +0900
commitb1e5c9fa9ac4399895bf312398c5d441baba0c3b (patch)
tree0eb4eac2b102d2d8bbdaf497895465dd442dd823 /src/backend/utils/adt/arrayfuncs.c
parentc99c7a4871187a8bcf717147ff08e05a49e678d5 (diff)
downloadpostgresql-b1e5c9fa9ac4399895bf312398c5d441baba0c3b.tar.gz
postgresql-b1e5c9fa9ac4399895bf312398c5d441baba0c3b.zip
Change logtape/tuplestore code to use int64 for block numbers
The code previously relied on "long" as type to track block numbers, which would be 4 bytes in all Windows builds or any 32-bit builds. This limited the code to be able to handle up to 16TB of data with the default block size of 8kB, like during a CLUSTER. This code now relies on a more portable int64, which should be more than enough for at least the next 20 years to come. This issue has been reported back in 2017, but nothing was done about it back then, so here we go now. Reported-by: Peter Geoghegan Reviewed-by: Heikki Linnakangas Discussion: https://postgr.es/m/CAH2-WznCscXnWmnj=STC0aSa7QG+BRedDnZsP=Jo_R9GUZvUrg@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/arrayfuncs.c')
0 files changed, 0 insertions, 0 deletions