PostgreSQL: Add load step and run_multiple_times.sh for dirty-folio regression repro - #6
Open
salvatoredipietro wants to merge 1 commit into
Open
PostgreSQL: Add load step and run_multiple_times.sh for dirty-folio regression repro#6salvatoredipietro wants to merge 1 commit into
salvatoredipietro wants to merge 1 commit into
Conversation
salvatoredipietro
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add load step and run_multiple_times.sh for dirty-folio regression repro
Split pgbench init (load step) from benchmark (run step) so an external
controller can restart PostgreSQL between them to build up dirty-page /
WBT state iteration-over-iteration. Adds PG_LDG_VERSION and
PG_HUGEPAGE_PAD_PERCENT knobs, fixes LDG package install for Debian vs
RPM, bumps pg_isready timeout to 180s, and adds ulimit -n guards.
run_multiple_times.sh drives the full repro: provisions once, then loops
N iterations (PG restart → load → PG restart → run) on a persistent
cluster so the regression accumulates predictably.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.