Add zstd back to `DataBackupConfiguration` compression enum

Open Beginner friendly
#305 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
88/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
go
Domain
api

Research direction

Open pkg/api/config.go and inspect DataBackupConfiguration.Compression and its doc comment. The work is complete when zstd is listed as a valid compression value, the comment reflects it, and xz remains excluded.

Written by the indexing model from the issue text.

Description

Add zstd back to DataBackupConfiguration compression enum

Summary

Barman 3.20.0 added --zstd support to barman-cloud-backup (EnterpriseDB/barman@0aa20706f2c430f7ccf44cd749c7838f40087ce0). This reverses the premise of #88 for zstd: it is now a valid base backup compression, alongside bzip2, gzip, lz4, and snappy.

DataBackupConfiguration.Compression in pkg/api/config.go still has +kubebuilder:validation:Enum=bzip2;gzip;lz4;snappy. Add zstd to the Enum and update the doc comment on the field. xz is still WAL-only and stays out.

Barman release notes for Release 3.20.0 (2026-08-27)

Add Zstd compression support for cloud backups

barman-cloud-backup now supports Zstd compression via the --zstd option.
Zstd offers a good balance between compression ratio and speed, making it
well-suited for cloud backup workloads.

Zstd compression requires the optional zstandard Python library to
be installed.

References: BAR-729.

Related Commits on EnterpriseDB/barman

  • EnterpriseDB/barman@0aa20706f2c430f7ccf44cd749c7838f40087ce0
  • EnterpriseDB/barman@00e61951bb997d353a87f69ad378e152f2405554
  • EnterpriseDB/barman@ed228ea789445e02fb4c199f30690942950e5813
  • EnterpriseDB/barman@8af084f2b1ae5b9235552dfc5c82174cf9cc0959

Related Issues and Pull Requests on cloudnative-pg/barman-cloud

  • #215
  • #216
Dominant language
Go
Stars
11
Forks
26
Avg merge
7h 53m
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudnative-pg/barman-cloud

All issues in cloudnative-pg/barman-cloud

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.