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
We've seen a few issues caused by DROP DATABASE CASCADE creating invalid descriptors, especially after the GC TTL ends.
We should add a test mode to the logic test suite that runs DROP DATABASE CASCADE at the end of tests, waits the GC TTL, and then runs validate on all table descriptors (or triggers the validate loop proposed in #51153. Hopefully, that would catch issues like #50712, #50997, #49940 and so on.
The text was updated successfully, but these errors were encountered:
jordanlewis
added
the
C-cleanup
Tech debt, refactors, loose ends, etc. Solution not expected to significantly change behavior.
label
Jul 9, 2020
We've seen a few issues caused by
DROP DATABASE CASCADE
creating invalid descriptors, especially after the GC TTL ends.We should add a test mode to the logic test suite that runs
DROP DATABASE CASCADE
at the end of tests, waits the GC TTL, and then runsvalidate
on all table descriptors (or triggers thevalidate
loop proposed in #51153. Hopefully, that would catch issues like #50712, #50997, #49940 and so on.The text was updated successfully, but these errors were encountered: