Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
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.

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

release-23.2: sql: allow DISCARD in read-only transactions #127548

Merged
merged 1 commit into from
Jul 24, 2024

Conversation

michae2
Copy link
Collaborator

@michae2 michae2 commented Jul 19, 2024

Backport 1/1 commits from #127298.

/cc @cockroachdb/release


To match PostgreSQL, allow DISCARD in read-only transactions.

Fixes: #124150

Release note (sql change): Fix a bug in which the DISCARD statement was disallowed with default_transaction_read_only = on.


Release justification: low-risk fix for ORM-breaking issue.

To match PostgreSQL, allow DISCARD in read-only transactions.

Fixes: cockroachdb#124150

Release note (sql change): Fix a bug in which the DISCARD statement was
disallowed with `default_transaction_read_only = on`.
@michae2 michae2 requested a review from a team as a code owner July 19, 2024 21:52
Copy link

blathers-crl bot commented Jul 19, 2024

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Backports should only be created for serious
    issues
    or test-only changes.
  • Backports should not break backwards-compatibility.
  • Backports should change as little code as possible.
  • Backports should not change on-disk formats or node communication protocols.
  • Backports should not add new functionality (except as defined
    here).
  • Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
  • All backports must be reviewed by the owning areas TL and one additional
    TL. For more information as to how that review should be conducted, please consult the backport
    policy
    .
If your backport adds new functionality, please ensure that the following additional criteria are satisfied:
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
  • Your backport must be accompanied by a post to the appropriate Slack
    channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Jul 19, 2024
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@michae2 michae2 requested a review from rafiss July 19, 2024 22:29
Copy link
Member

@yuzefovich yuzefovich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 2 of 2 files at r1, all commit messages.
Reviewable status: :shipit: complete! 0 of 0 LGTMs obtained (waiting on @mgartner and @rafiss)

@michae2 michae2 merged commit cce43d8 into cockroachdb:release-23.2 Jul 24, 2024
5 of 6 checks passed
@michae2 michae2 deleted the backport23.2-127298 branch July 24, 2024 14:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Label PR's that are backports to older release branches
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants