-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql: hang possible due to bad version bookkeeping #87672
Copy link
Copy link
Closed
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.GA-blockerT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)branch-release-22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2
Description
Describe the problem
Consider the following test:
CREATE DATABASE db;
USE db;
CREATE SCHEMA sc;
BEGIN;
CREATE SCHEMA sc2;
SELECT * FROM crdb_internal.tables;
DROP SCHEMA sc CASCADE;
COMMIT;This now fails, and it was broken in #87067
Additional context
This was discovered while investigating #78478.
Jira issue: CRDB-19466
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.GA-blockerT-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)branch-release-22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2Used to mark GA and release blockers, technical advisories, and bugs for 22.2