-
Notifications
You must be signed in to change notification settings - Fork 2
Comparing changes
Open a pull request
base repository: postgresql-cfbot/postgresql
base: cf/5955~1
head repository: postgresql-cfbot/postgresql
compare: cf/5955
- 9 commits
- 15 files changed
- 2 contributors
Commits on Dec 6, 2025
-
Refactor: pg_waldump: Move some declarations to new pg_waldump.h
This change prepares for a second source file in this directory to support reading WAL from tar files. Common structures, declarations, and functions are being exported through this include file so they can be used in both files.
Configuration menu - View commit details
-
Copy full SHA for 04e5c84 - Browse repository at this point
Copy the full SHA 04e5c84View commit details -
Refactor: pg_waldump: Separate logic used to calculate the required r…
…ead size. This refactoring prepares the codebase for an upcoming patch that will support reading WAL from tar files. The logic for calculating the required read size has been updated to handle both normal WAL files and WAL files located inside a tar archive.
Configuration menu - View commit details
-
Copy full SHA for 9594f35 - Browse repository at this point
Copy the full SHA 9594f35View commit details -
Refactor: pg_waldump: Restructure TAP tests.
Restructured some tests to run inside a loop, facilitating their re-execution for decoding WAL from tar archives. == NOTE == This is not intended to be committed separately. It can be merged with the next patch, which is the main patch implementing this feature.
Configuration menu - View commit details
-
Copy full SHA for f230b05 - Browse repository at this point
Copy the full SHA f230b05View commit details -
pg_waldump: Add support for archived WAL decoding.
pg_waldump can now accept the path to a tar archive containing WAL files and decode them. This feature was added primarily for pg_verifybackup, which previously disabled WAL parsing for tar-formatted backups. Note that this patch requires that the WAL files within the archive be in sequential order; an error will be reported otherwise. The next patch is planned to remove this restriction.
Configuration menu - View commit details
-
Copy full SHA for 19d33db - Browse repository at this point
Copy the full SHA 19d33dbView commit details -
pg_waldump: Remove the restriction on the order of archived WAL files.
With previous patch, pg_waldump would stop decoding if WAL files were not in the required sequence. With this patch, decoding will now continue. Any WAL file that is out of order will be written to a temporary location, from which it will be read later. Once a temporary file has been read, it will be removed.
Configuration menu - View commit details
-
Copy full SHA for b49e566 - Browse repository at this point
Copy the full SHA b49e566View commit details -
pg_verifybackup: Delay default WAL directory preparation.
We are not sure whether to parse WAL from a directory or an archive until the backup format is known. Therefore, we delay preparing the default WAL directory until the point of parsing. This delay is harmless, as the WAL directory is not used elsewhere.
Configuration menu - View commit details
-
Copy full SHA for d25e69c - Browse repository at this point
Copy the full SHA d25e69cView commit details -
pg_verifybackup: Rename the wal-directory switch to wal-path
With previous patches to pg_waldump can now decode WAL directly from tar files. This means you'll be able to specify a tar archive path instead of a traditional WAL directory. To keep things consistent and more versatile, we should also generalize the input switch for pg_verifybackup. It should accept either a directory or a tar file path that contains WALs. This change will also aligning it with the existing manifest-path switch naming. == NOTE == The corresponding PO files require updating due to this change.
Configuration menu - View commit details
-
Copy full SHA for ae8fb3c - Browse repository at this point
Copy the full SHA ae8fb3cView commit details -
pg_verifybackup: enabled WAL parsing for tar-format backup
Now that pg_waldump supports decoding from tar archives, we should leverage this functionality to remove the previous restriction on WAL parsing for tar-backed formats.
Configuration menu - View commit details
-
Copy full SHA for 67ff887 - Browse repository at this point
Copy the full SHA 67ff887View commit details -
[CF 5955] v9 - pg_waldump: support decoding of WAL inside tarfile
This branch was automatically generated by a robot using patches from an email thread registered at: https://commitfest.postgresql.org/patch/5955 The branch will be overwritten each time a new patch version is posted to the thread, and also periodically to check for bitrot caused by changes on the master branch. Patch(es): https://www.postgresql.org/message-id/CAAJ_b94SEcBVJcsp0Y1-YvLqZWBHPQH4FhRzSJfaH_ah_eL_FQ@mail.gmail.com Author(s): Amul Sul
Commitfest Bot committedDec 6, 2025 Configuration menu - View commit details
-
Copy full SHA for 4d929ad - Browse repository at this point
Copy the full SHA 4d929adView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff cf/5955~1...cf/5955