release-22.1: make enable_implicit_transaction_for_batch_statements false by default; or false for DDL #77967
Labels
branch-release-22.1
Used to mark GA and release blockers, technical advisories, and bugs for 22.1
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
GA-blocker
The new enable_implicit_transaction_for_batch_statements session var defaults to true. This is a bug fix, but the change can cause pain since we have differing behavior for schema changes inside or outside a transaction.
To ease the transition, we should make v22.1 default the setting to false. Or we can be a bit more aggressive and set it to true, but keep the old behavior if schema changes, BACKUP, RESTORE, or IMPORT are involved.
Jira issue: CRDB-13876
The text was updated successfully, but these errors were encountered: