aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistget.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2017-04-23 15:48:31 -0700
committerAndres Freund <andres@anarazel.de>2017-04-23 15:54:58 -0700
commit81ff04deda21e016e0e1d4ea1755ccb14c47c871 (patch)
tree75096c5f9d90a05b546d849ad910ff392a49be35 /src/backend/access/gist/gistget.c
parenta66e01bbcc8808674ade41d38cfba711a36b8b15 (diff)
downloadpostgresql-81ff04deda21e016e0e1d4ea1755ccb14c47c871.tar.gz
postgresql-81ff04deda21e016e0e1d4ea1755ccb14c47c871.zip
Zero padding in replication origin's checkpointed on disk-state.
This seems to be largely cosmetic, avoiding valgrind bleats and the like. The uninitialized padding influences the CRC of the on-disk entry, but because it's also used when verifying the CRC, that doesn't cause spurious failures. Backpatch nonetheless. It's a bit unfortunate that contrib/test_decoding/sql/replorigin.sql doesn't exercise the checkpoint path, but checkpoints are fairly expensive on weaker machines, and we'd have to stop/start for that to be meaningful. Author: Andres Freund Discussion: https://postgr.es/m/20170422183123.w2jgiuxtts7qrqaq@alap3.anarazel.de Backpatch: 9.5, where replication origins were introduced
Diffstat (limited to 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions