aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor
diff options
context:
space:
mode:
authorPeter Geoghegan <pg@bowt.ie>2023-04-19 10:42:39 -0700
committerPeter Geoghegan <pg@bowt.ie>2023-04-19 10:42:39 -0700
commit50547a3fae0ce62e74c1d2175c7949937f2c69fc (patch)
treee7d7b434c990970111d5d53d74348233c112f768 /src/backend/executor
parent9e1e9d6560ec60535289ac15729a08e2f7cf4165 (diff)
downloadpostgresql-50547a3fae0ce62e74c1d2175c7949937f2c69fc.tar.gz
postgresql-50547a3fae0ce62e74c1d2175c7949937f2c69fc.zip
Fix wal_consistency_checking enhanced desc output.
Recent enhancements to rmgr desc routines that made the output summarize certain block data (added by commits 7d8219a4 and 1c453cfd) dealt with records that lack relevant block data (and so have nothing to give a more detailed summary of) by testing !DecodedBkpBlock.has_image. As a result, more detailed descriptions of block data were not output when wal_consistency_checking was enabled. This bug affected records with summarizable block data that also happened to have an FPI that the REDO routine isn't supposed to apply (FPIs used for consistency checking purposes only). The presence of such an FPI was incorrectly taken to indicate the absence of block data. To fix, test DecodedBkpBlock.has_data, not !DecodedBkpBlock.has_image. This is the exact condition that we care about, not an inexact proxy. Author: Peter Geoghegan <pg@bowt.ie> Discussion: https://postgr.es/m/CAH2-Wzm5Sc9cBg1qWV_cEBfLNJCrW9FjS-SoHVt8FLA7Ldn8yg@mail.gmail.com
Diffstat (limited to 'src/backend/executor')
0 files changed, 0 insertions, 0 deletions