aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistsplit.c
diff options
context:
space:
mode:
authorTeodor Sigaev <teodor@sigaev.ru>2018-04-19 11:28:03 +0300
committerTeodor Sigaev <teodor@sigaev.ru>2018-04-19 11:28:03 +0300
commitff4943042f9761fb4e84432da563f43eb3559a3b (patch)
tree4f7fe8e130214e7e8bcca65bbe5f7a4bdfa2af4c /src/backend/access/gist/gistsplit.c
parentf97f0c921ae56bb16e466f3c9d6c504f4a96a539 (diff)
downloadpostgresql-ff4943042f9761fb4e84432da563f43eb3559a3b.tar.gz
postgresql-ff4943042f9761fb4e84432da563f43eb3559a3b.zip
Fix datatype for number of heap tuples during last cleanup
It appears that new fields introduced in 857f9c36 have inconsistent datatypes: BTMetaPageData.btm_last_cleanup_num_heap_tuples is of float4 type, while xl_btree_metadata.last_cleanup_num_heap_tuples is of double type. IndexVacuumInfo.num_heap_tuples, which is a source of values for both former fields is of double type. So, make both those fields in BTMetaPageData and xl_btree_metadata use float8 type in order to match the precision of the source. That shouldn't be double type, because we always use types with explicit width in WAL. Patch introduces incompatibility of on-disk format since 857f9c36 commit, but that versions never was released, so just bump catalog version to avoid possible confusion. Author: Alexander Korortkov
Diffstat (limited to 'src/backend/access/gist/gistsplit.c')
0 files changed, 0 insertions, 0 deletions