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.1: sql: add plpgsql parser for telemetry purposes #103026

Merged
merged 11 commits into from
May 11, 2023

Conversation

e-mbrown
Copy link
Contributor

@e-mbrown e-mbrown commented May 10, 2023

Backport 11/11 commits from #98147.

/cc @cockroachdb/release


Informs: #91569

This commit adds the in use portions of the plpgsql parser from #91606.

Release note: None
Release justification: The PR allows us to parse some plpggsql statements but doesn't add functionality.

chengxiong-ruan and others added 10 commits May 10, 2023 10:39
This commit adds the code generation portion of the parser.
The parser does not parse statements yet.
This commit also creates a base scanner struct so that the plpgsql
and sql scanner can share methods. The two scanners have their
own language specific scan methods.

Release note: None
Adds the first test which parses an empty function or
function with bare sql queries.

Release note: None
This commit adds `lexer.ReadSqlExpressionStr()` which
gives access to the return type of a plpgsql function.

This commit also adds grammar rules and AST for
`stmt_if`

Release note: None
This commit adds AST and grammar rules for
`decl_header` and `stmt_assert`

Release note: None
This commit adds the AST and grammar rules for `stmt_call`,
`stmt_close`, `stmt_dynaexec`, and `stmt_exit`

Release note: None
This commit adds the AST and grammar rules for
`stmt_assign` and `stmt_getdiag`

Release note: None
This commit adds portions of the logic to parse `stmt_case`.
Does not yet support ELSE, sql statements in THEN body, or END CASE (it
uses an ENDCASE hack).

Release note: None
This commit corrects the grammar rules for `stmt_case`.

Release note: None
This commit corrects the grammar rules and AST of
`stmt_if`, `elsif`, `else` statements.

Release note: None
This commit adds logic for `stmt_open`

Release note: None
@e-mbrown e-mbrown requested review from chengxiong-ruan and a team May 10, 2023 15:06
@e-mbrown e-mbrown requested review from a team as code owners May 10, 2023 15:06
@e-mbrown e-mbrown requested a review from a team May 10, 2023 15:06
@e-mbrown e-mbrown requested review from a team as code owners May 10, 2023 15:06
@e-mbrown e-mbrown requested a review from a team May 10, 2023 15:06
@e-mbrown e-mbrown requested a review from a team as a code owner May 10, 2023 15:06
@e-mbrown e-mbrown requested a review from mgartner May 10, 2023 15:06
@blathers-crl
Copy link

blathers-crl bot commented May 10, 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?

@cockroach-teamcity
Copy link
Member

This change is Reviewable

This commit makes Statement generic so it can be shared between
the sql and plpgsql parsers.

Release note: None
@e-mbrown e-mbrown merged commit 4334736 into cockroachdb:release-23.1 May 11, 2023
@e-mbrown e-mbrown deleted the backport23.1-98147 branch June 6, 2023 13:10
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.

5 participants