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-22.2: sql: handle mixed-case for pg_get_serial_sequence #107371

Merged
merged 1 commit into from Jul 21, 2023

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Jul 21, 2023

Backport 1/1 commits from #107358 on behalf of @rafiss.

/cc @cockroachdb/release


fixes #107234
Release note (bug fix): The pg_get_serial_sequence builtin function can now handle mixed-case names correctly.


Release justification: bug fix

Release note (bug fix): The pg_get_serial_sequence builtin function can
now handle mixed-case names correctly.
@blathers-crl blathers-crl bot requested a review from a team as a code owner July 21, 2023 18:10
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2-107358 branch from 8a30110 to b3a35f4 Compare July 21, 2023 18:10
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jul 21, 2023
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2-107358 branch from be41e4d to 395ef06 Compare July 21, 2023 18:10
@blathers-crl
Copy link
Author

blathers-crl bot commented Jul 21, 2023

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • 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.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl blathers-crl bot requested a review from fqazi July 21, 2023 18:10
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@rafiss rafiss merged commit 7e14f0c into release-22.2 Jul 21, 2023
5 of 6 checks passed
@rafiss rafiss deleted the blathers/backport-release-22.2-107358 branch July 21, 2023 19:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants