OPtimize storing zero page image in WAL as FPI #824
+23
−13
Conversation
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
knizhnik
force-pushed
the
zero_page_optimization_v15
branch
from
b7dd4f7 to
b7509d4
Compare
mmeent-databricks
approved these changes
Dec 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PG>=16 has optimization for storing zero page in FPI. When storing page as FPIN in WAL records, Postgres excludes page hole (space betweenpd_upper and pd_lower), but it not able to handle zero page (hole size=page size).
It allows to minimize WAL size in case of walloging smgrzeroextend.
PG14/15 doesn't have smgrzeroextend and so has not such optimization.