Base backups are single-threaded and ignore concurrency settings

Open

#906 opened on May 12, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 52/100

Issue type: Feature
Clarity: Mostly clear
Activity status: Quiet
Tech stack: go, postgresql
Domain: cloud, databases, performance

Research direction

Start by tracing the plugin-barman-cloud base-backup upload path and compare it with WAL archiving's maxParallel handling. Determine how the data upload can honor a configurable parallel-job setting; done means the base backup phase supports parallel uploads without changing the existing default behavior.

Written by the indexing model from the issue text.

Description

bug

The plugin-barman-cloud performs base backups using a single upload stream. Unlike WAL archiving (which supports maxParallel), there is no way to parallelize the data backup phase. This results in bottlenecks for large databases.

This option:

$ kubectl explain objectstore.spec.configuration.data.jobs
GROUP:      barmancloud.cnpg.io
KIND:       ObjectStore
VERSION:    v1

FIELD: jobs <integer>


DESCRIPTION:
    The number of parallel jobs to be used to upload the backup, defaults
    to 2

is not applicable due to limitation (only for rsync):
https://github.com/EnterpriseDB/barman/blob/ff040cd1feee805da3e4662a187c583f8730dfab/docs/user_guide/configuration.rst?plain=1#L336

parallel_jobs

Controls the number of parallel workers used to copy files during backup or recovery.
It must be a positive integer. Default is 1.

note::
Applies only when backup_method = rsync.

Dominant language: Go
Stars: 192
Forks: 75
Avg merge: 1d 7h
Merged PRs (30d): 17

Contributor guide

Open the contributing guide

First steps

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

Similar issues

ci: macOS contributor nightly fails to build aws-lc-fips-sys (Could not find Go) Open

bug github_actions

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

registrystack/registry-stack#1393 · Opened Sep 24, 2026
self-host checker: `write` with the wrong argument count is not E004 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

JakeChampion/lang#10213 · Opened Sep 24, 2026
Bump protobufjs to >=7.5.5 to address GHSAs (transitive via @oasisprotocol/client) Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

oasisprotocol/oasis-sdk#2523 · Opened Sep 24, 2026
x/vulndb: suggestion regarding GO-2026-6452 Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

golang/vulndb#6587 · Opened Sep 24, 2026
authentik_source_oauth: access_token_url/authorization_url/oidc_jwks_url/profile_url cause a permanent diff when oidc_well_known_url is set Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

goauthentik/terraform-provider-authentik#981 · Opened Sep 24, 2026

More Go issues