Skip to content

Allow specifying REVOKE after GRANT in the same statement#27

Draft
joelynch wants to merge 1 commit intov25.3.7.194-lts-aivenfrom
joelynch/grant-revoke
Draft

Allow specifying REVOKE after GRANT in the same statement#27
joelynch wants to merge 1 commit intov25.3.7.194-lts-aivenfrom
joelynch/grant-revoke

Conversation

@joelynch
Copy link

This allows an atomic partial revoke WITH REPLACE OPTION. So the full grants / revokes can be done in one statement, without race conditions or worries about a partial revoke failing.

Changelog category (leave one):

  • New Feature
  • Experimental Feature
  • Improvement
  • Performance Improvement
  • Backward Incompatible Change
  • Build/Testing/Packaging Improvement
  • Documentation (changelog entry is not required)
  • Critical Bug Fix (crash, data loss, RBAC) or LOGICAL_ERROR
  • Bug Fix (user-visible misbehavior in an official stable release)
  • CI Fix or Improvement (changelog entry is not required)
  • Not for changelog (changelog entry is not required)

Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):

...

Documentation entry for user-facing changes

  • Documentation is written (mandatory for new features)

This allows an atomic partial revoke WITH REPLACE OPTION. So the full
grants / revokes can be done in one statement, without race conditions
or worries about a partial revoke failing.
@joelynch joelynch changed the title Update autogenerated version to 25.4.1.1 and contributors Allow specifying REVOKE after GRANT in the same statement Feb 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant