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
sql,multiregion: prevent DROP REGION in user DB from cleaning up system.sql_instances
Previously, DROP REGION cleanup logic for system.sql_instances was
unintentionally applied to all databases when in multiregion setup,
not just the system database. The original intent was to only perform
this cleanup when extending `DROP REGION` for the system database.
However, the logic leaked through, affecting user databases as well.
This PR implements the fix described in #151789, and after a quick check
of these changes with the blocked tests in the #150730, this fixes them
plus passes the original tests created for testing drop region in system
database.
Epic: None
Fixes: #151789
Release note: None
Co-authored-by: Shubham Dhama <[email protected]>
{"ALTER PARTITION \"us-east3\" OF INDEX system.public.lease@primary CONFIGURE ZONE USING\n\tnum_voters = 3,\n\tvoter_constraints = '[+region=us-east3]',\n\tlease_preferences = '[[+region=us-east3]]'"},
599
599
})
600
600
}
601
+
602
+
// TestDropRegionFromUserDatabaseCleansUpSystemTables verifies that
603
+
// dropping a region from a user database doesn't remove rows
0 commit comments