Treat pg_basebackup throttling and WAL streaming as separate budgets

Budget data-copy traffic and streamed WAL separately when throttling a PostgreSQL base backup.

Source facts

In PostgreSQL 17, pg_basebackup can stream WAL alongside the base backup using its stream collection method. That opens a second replication connection, so the run needs two replication connections rather than one. The max-rate setting limits data-directory transfer, but it limits WAL transfer only when the collection method is fetch. Consequently, setting a base-backup rate cap does not also cap the separate streamed WAL traffic. An incremental backup also requires combination with its prerequisite backups before use.

Source: PostgreSQL 17 — pg_basebackup.

Applicability

This guidance applies to PostgreSQL 17 pg_basebackup planning, particularly streamed-WAL backups. It does not prescribe a transfer rate or infer available replication capacity for a particular server.

DSE recommendation

DSE recommends putting data transfer, WAL generation, replication connections, and destination capacity into the same change worksheet. State explicitly which traffic the configured rate limit controls. Prefer a conservative trial during a supervised window before increasing throughput. Keep the selected WAL method and any incremental dependencies attached to the backup record, so recovery staff do not mistake an individual incremental directory for a self-contained recovery image.

Verification

Use a test cluster to observe replication connections and data transfer with the intended WAL mode. Confirm that monitoring distinguishes data-copy throughput from WAL traffic. Reconstruct and start the resulting backup in isolation, including the combination stage if an incremental backup was selected.

Official reference

PostgreSQL 17 — pg_basebackup. Reviewed October 15, 2026.