Skip to content

Improvement #8750 - Downgrade compatibility supporting restore of v6 backups - #8751

Open
asfernandes wants to merge 2 commits into
v5.0-releasefrom
work/gh-8750/v5-schema-downgrade
Open

asfernandes wants to merge 2 commits into
v5.0-releasefrom
work/gh-8750/v5-schema-downgrade

Conversation

@asfernandes

Copy link
Copy Markdown
Member

No description provided.

@asfernandes asfernandes linked an issue Sep 22, 2025 that may be closed by this pull request
@asfernandes
asfernandes force-pushed the work/gh-8750/v5-schema-downgrade branch from 40332be to 1dc6e00 Compare November 6, 2026 01:01
@asfernandes

Copy link
Copy Markdown
Member Author

@dyemanov I do think schema BLR codes are stable in master. Can merge this in v5?

@asfernandes
asfernandes requested a review from dyemanov November 6, 2026 01:03
@sim1984

sim1984 commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

Among the large features that haven't been committed yet:

JSON — new BLR;
ROW-type — new BLR, new system tables;
SQL/MED — at the very least, new system tables.

Perhaps we should wait until a feature freeze is announced?

@asfernandes

Copy link
Copy Markdown
Member Author

Schemas has downgrade compatibility only because it's automatic, user cannot avoid them.

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.

Downgrade compatibility supporting restore of v6 backups

2 participants