aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/dbcommands.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2024-02-01 11:46:30 -0500
committerRobert Haas <rhaas@postgresql.org>2024-02-01 11:52:26 -0500
commit19a829a3270fb083b3d6ae967cd3b3c02a170a38 (patch)
treebc7a24aaae69d1263a7d3cd0b8f27894a4f5733f /src/backend/commands/dbcommands.c
parent21912e3c0262e2cfe64856e028799d6927862563 (diff)
downloadpostgresql-19a829a3270fb083b3d6ae967cd3b3c02a170a38.tar.gz
postgresql-19a829a3270fb083b3d6ae967cd3b3c02a170a38.zip
Continue my quest to make 002_blocks.pl pass reliably.
The latest buildfarm failures show that after the insert, we don't actually wait long enough for WAL summarization to catch up, apparently because the on disk state gets updated before the in-memory state, and so by checking the on disk state to see whether we're caught up and then the in-memory state to see where exactly how far we've progressed, we can, if unlucky, derive an older value of summarized_lsn, messing up the rest of the test. Attempt to fix this by using pg_available_wal_summaries() everywhere in the test and pg_get_wal_summarizer_state() nowhere. Per buildfarm.
Diffstat (limited to 'src/backend/commands/dbcommands.c')
0 files changed, 0 insertions, 0 deletions