sql: database exists in SHOW DATABASE list after DROP #18286
Labels
A-schema-changes
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
S-3-ux-surprise
Issue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.
@HeikoOnnebrink (from #17524) recently ran into some strangeness around dropping tables.
He dropped two tables but they continued to show up in SHOW TABLES queries. If he issued
further DROP TABLE requests, he would get an error
pq: relation "requests" does not exist
.Looking quickly through his logs, this line stood out:
Later he tried to DROP DATABASE. Even after he issued this, the database remained in his
SHOW DATABASES queries. However, when he tries to do anything in the database,
he gets an error:
If we want to investigate the corrupted state, we have access to this cluster via a Cisco WebEx session (you'll need a chrome plugin) at a meeting link that can be activated by Heiko on Gitter (he'll supervise while you are connected).
The text was updated successfully, but these errors were encountered: