You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Downgrade compatibility supporting restore of v6 backups #8750
It should be possible to downgrade v6 databases with gbak/restore into older versions (mainly v5).
That should be possible if there is no new feature usage. That normally happens, but due to schemas (that is not a opt-in feature), it requires additional code.
A v6 database with multiple schemas usage should be downgradable provided that there is no duplicate object names using different schemas.
This issue can be solved by introducing a new set of system table and leave old set for compatibility only. Only objects from schemas PUBLIC and SYSTEM should be visible in compatibility system tables. In this case gbak from v5 will be able to make backup of v6 database as usual.
Reacted by Adriano dos Santos Fernandes and Simonov Denis
Activity
asfernandes commentedon Sep 22, 2025
Suggested test below. Should create a v6 database, backup and restore into v5. Result should match v6.
aafemt commentedon Sep 22, 2025
This issue can be solved by introducing a new set of system table and leave old set for compatibility only. Only objects from schemas
PUBLICandSYSTEMshould be visible in compatibility system tables. In this case gbak from v5 will be able to make backup of v6 database as usual.