Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sql: create a new option "strict DDL atomicity" to guarantee that XXA00 cannot happen in schema changes #108737

Closed
knz opened this issue Aug 14, 2023 · 0 comments · Fixed by #42063
Closed

sql: create a new option "strict DDL atomicity" to guarantee that XXA00 cannot happen in schema changes #108737

knz opened this issue Aug 14, 2023 · 0 comments · Fixed by #42063
Assignees
@knz
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)

Comments

@knz
Copy link
Contributor

knz commented Aug 14, 2023 •
edited by cockroach-jira-scripts
Loading

See the discussion in #42061. We want to give customer a way to ensure that no error XXA00 can ever be produced by restricting which DDL they can use in explicit transactions.

Epic: CRDB-28893

Jira issue: CRDB-30617
@knz knz added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Aug 14, 2023
@knz knz self-assigned this Aug 14, 2023
@knz knz mentioned this issue Aug 14, 2023
Merged
@craig craig bot closed this as completed in 8795698 Aug 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@knz knz

Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

sql: new opt-in option strict_ddl_atomicity knz/cockroach
1 participant
@knz