Skip to content

Conversation

@qw4990
Copy link
Contributor

@qw4990 qw4990 commented Feb 10, 2026

First-time contributors' checklist

What is changed, added or deleted? (Required)

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

@ti-chi-bot
Copy link

ti-chi-bot bot commented Feb 10, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jackysp for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the missing-translation-status This PR does not have translation status info. label Feb 10, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @qw4990, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request updates the documentation for the PLAN REPLAYER feature, specifically to reflect its enhanced capability to dump multiple SQL statements in a single operation. The changes clarify the new command syntax, detail the resulting output file structure for multi-statement dumps, and include a practical example to guide users. This improves the utility and clarity of the PLAN REPLAYER documentation.

Highlights

  • New Syntax for Multi-Statement Dumps: Introduced a new syntax for the PLAN REPLAYER DUMP command, allowing users to specify multiple SQL statements directly within the command to be dumped at once.
  • Updated ZIP File Structure Documentation: Added detailed explanations of the exported ZIP file structure, differentiating between single and multiple SQL statement dumps, and outlining how sql and explain files are organized for multi-statement scenarios.
  • Example for Multi-Statement Dumps: Provided a clear example demonstrating the usage of the new PLAN REPLAYER DUMP syntax with multiple SQL statements, enhancing user understanding.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • sql-plan-replayer.md
    • Added new PLAN REPLAYER DUMP syntax for specifying multiple SQL statements.
    • Updated the description of information exported by TiDB to reflect support for multiple statements.
    • Documented the structure of the exported ZIP file for both single and multiple SQL statement dumps.
    • Included a new example demonstrating how to dump multiple SQL statements directly in the command.
Activity
  • No specific activity (comments, reviews, etc.) has occurred on this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@ti-chi-bot ti-chi-bot bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 10, 2026
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request updates the documentation for PLAN REPLAYER to include the new syntax for dumping multiple SQL statements at once. The changes are accurate and add a helpful example. I have provided a couple of suggestions to improve clarity and conciseness, in line with the repository's style guide.

Comment on lines +35 to +38
Depending on whether you dump a single SQL statement or multiple SQL statements, the structure of the exported ZIP file is as follows:

- For a single SQL statement, the ZIP file includes `sql/sql0.sql` and `explain.txt`.
- For multiple SQL statements, the ZIP file includes `sql/sql0.sql`, `sql/sql1.sql`, ... and the corresponding `explain/explain0.txt`, `explain/explain1.txt`, ..., together with schema and statistics files for the referenced tables.
Copy link
Contributor

Choose a reason for hiding this comment

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

low

To improve clarity, this section can be rephrased to be more direct and avoid using '...'.

Suggested change
Depending on whether you dump a single SQL statement or multiple SQL statements, the structure of the exported ZIP file is as follows:
- For a single SQL statement, the ZIP file includes `sql/sql0.sql` and `explain.txt`.
- For multiple SQL statements, the ZIP file includes `sql/sql0.sql`, `sql/sql1.sql`, ... and the corresponding `explain/explain0.txt`, `explain/explain1.txt`, ..., together with schema and statistics files for the referenced tables.
The structure of the exported ZIP file depends on whether you dump a single SQL statement or multiple SQL statements:
- For a single SQL statement, the ZIP file includes `sql/sql0.sql` and `explain.txt`.
- For multiple SQL statements, the ZIP file includes SQL files such as `sql/sql0.sql` and `sql/sql1.sql`, their corresponding explain files such as `explain/explain0.txt` and `explain/explain1.txt`, and the schema and statistics files for the referenced tables.
References
  1. The style guide emphasizes clarity, simplicity, and readability (line 14). The suggested change improves readability by making the sentence structure simpler and avoiding the informal '...'. (link)

);
```

Alternatively, when there are multiple SQL statements, you can obtain the result of the `PLAN REPLAYER DUMP` execution using a file. The results of multiple SQL statements are separated by `;` in this file.
Copy link
Contributor

Choose a reason for hiding this comment

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

low

This sentence can be simplified for better readability and to be more direct for the user, in line with the style guide's preference for using the second person ('you').

Suggested change
Alternatively, when there are multiple SQL statements, you can obtain the result of the `PLAN REPLAYER DUMP` execution using a file. The results of multiple SQL statements are separated by `;` in this file.
Alternatively, you can dump multiple SQL statements from a file. In this file, separate SQL statements with a semicolon (`;`).
References
  1. The style guide recommends writing in the second person ('you') (line 22) and preferring clarity and simplicity (line 14). The suggested change makes the instruction more direct and easier for the user to follow. (link)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

missing-translation-status This PR does not have translation status info. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant