Clarify CSv3 backup format is system-determined (not selectable)#20
Draft
lvangool wants to merge 1 commit into
Draft
Conversation
CSv2/Maestro exposes a binary/text backup format choice; CSv3 does not. On CSv3 the format is fixed by the backup system the database engine uses (e.g. Barman for CNPG-managed Postgres). Customers migrating from CSv2 looked for the toggle and were confused by its absence. Adds a short "Backup format" section explaining this and pointing users who need a portable dump at standard engine export tooling (pg_dump, mysqldump). Linear: SUP-1012 (closed Invalid; this clarification stands on its own) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a short "Backup format" section to
databases/3/database-backups.mdxexplaining that, unlike CSv2/Maestro, CSv3 has no customer-selectable binary/text format toggle — the format is fixed by the backup system the database engine uses (e.g. Barman for CNPG-managed Postgres). Points users who need a portable dump at standard engine export tooling (pg_dump,mysqldump).Why
On HS #33560 a customer (Latitude) went looking for the binary/text format option that exists on CSv2 and was confused by its absence on CSv3. The originating ticket (SUP-1012) assumed the toggle existed but was undocumented; in fact it doesn't exist on CSv3 at all. The ticket was closed as Invalid (premise incorrect), but the underlying customer confusion is real and this small clarification addresses it.
Linear
Test plan
yarn validate:mdxpasses🤖 Generated with Claude Code