Skip to content

Disable fetch wal-method for pg_basebackup with Percona features #533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

dAdAbird
Copy link
Member

As it may clash with encrypted WAL streaming.

Hide the fetch option from the usage output and throw an error if it is used.

As it may clash with encrypted WAL streaming.

Hide the fetch option from the usage output and throw an error if it is used.
@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.08%. Comparing base (f508287) to head (bb76ff7).

❌ Your project status has failed because the head coverage (82.08%) is below the target coverage (90.00%). You can increase the head coverage or adjust the target coverage.

Additional details and impacted files
@@                Coverage Diff                 @@
##           TDE_REL_17_STABLE     #533   +/-   ##
==================================================
  Coverage              82.08%   82.08%           
==================================================
  Files                     25       25           
  Lines                   3170     3170           
  Branches                 505      505           
==================================================
  Hits                    2602     2602           
  Misses                   460      460           
  Partials                 108      108           
Components Coverage Δ
access 83.42% <ø> (ø)
catalog 87.60% <ø> (ø)
common 77.77% <ø> (ø)
encryption 72.97% <ø> (ø)
keyring 73.21% <ø> (ø)
src 94.15% <ø> (ø)
smgr 95.90% <ø> (ø)
transam ∅ <ø> (∅)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@AndersAstrand
Copy link
Collaborator

Are we sure we want to change these tools for people running our distribution without wal encryption turned on? I'm not convinced that's what we want to do.

@dAdAbird
Copy link
Member Author

dAdAbird commented Aug 18, 2025

Yes, I think we can abandon this idea after the introduction of --encrypt-wal flag

@dAdAbird
Copy link
Member Author

Seems like having just the --encrypt-wal flag is a better idea: #537

@dAdAbird dAdAbird closed this Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants