Incorrect state of new encrypted files when ALTERing mixed encrypted/not encrypted inherited tables

Description

This scenario is not realistic, as the tables in the inheritance chain have different encryption status, but it is still a bug, we mess up new files when we modify tables in this scenario, for example:

How to document

None

How to test

None

Activity

Show:

Details

Assignee

Reporter

Priority

Smart Checklist

Created 5 days ago
Updated 5 days ago