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

Fix EBNF for SET PASSWORD and SHOW ENGINES #17304

Merged
merged 2 commits into from
Apr 22, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion faq/monitor-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ The monitoring system of TiDB consists of Prometheus and Grafana. From the dashb

Yes. Find the startup script on the machine where Prometheus is started, edit the startup parameter and restart Prometheus.

```config
```
--storage.tsdb.retention="60d"
```

Expand Down
2 changes: 1 addition & 1 deletion information-schema/information-schema-slow-query.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ DESC SLOW_QUERY;

The output is as follows:

```sqlsql
```
+-------------------------------+---------------------+------+------+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------------------------+---------------------+------+------+---------+-------+
Expand Down
2 changes: 1 addition & 1 deletion sql-statements/sql-statement-set-password.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This statement changes the user password for a user account in the TiDB system d

## Synopsis

```enbf+diagram
```ebnf+diagram
SetPasswordStmt ::=
"SET" "PASSWORD" ( "FOR" Username )? "=" ( stringLit | "PASSWORD" "(" stringLit ")" )
```
Expand Down
2 changes: 1 addition & 1 deletion sql-statements/sql-statement-show-engines.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ This statement is used to list all supported storage engines. The syntax is incl

## Synopsis

```enbf+diagram
```ebnf+diagram
ShowEnginesStmt ::=
"SHOW" "ENGINES" ShowLikeOrWhere?

Expand Down
6 changes: 3 additions & 3 deletions sync-diff-inspector/sync-diff-inspector-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -182,7 +182,7 @@ sync-diff-inspector sends progress information to `stdout` when running. Progres
>
> To ensure the display effect, keep the display window width above 80 characters.

```progress
```
A total of 2 tables need to be compared

Comparing the table structure of ``sbtest`.`sbtest96`` ... equivalent
Expand All @@ -193,7 +193,7 @@ _____________________________________________________________________________
Progress [==========================================================>--] 98% 193/200
```

```progress
```
A total of 2 tables need to be compared

Comparing the table structure of ``sbtest`.`sbtest96`` ... equivalent
Expand Down Expand Up @@ -245,7 +245,7 @@ The running sync-diff-inspector periodically (every 10 seconds) prints the progr

After the check is finished, sync-diff-inspector outputs a report. It is located at `${output}/summary.txt`, and `${output}` is the value of `output-dir` in the `config.toml` file.

```summary
```
+---------------------+--------------------+----------------+---------+-----------+
| TABLE | STRUCTURE EQUALITY | DATA DIFF ROWS | UPCOUNT | DOWNCOUNT |
+---------------------+--------------------+----------------+---------+-----------+
Expand Down
2 changes: 1 addition & 1 deletion tidb-cloud/migrate-from-op-tidb.md
Original file line number Diff line number Diff line change
Expand Up @@ -172,7 +172,7 @@ Do the following to export data from the upstream TiDB cluster to Amazon S3 usin

3. Run Dumpling to export data to the Amazon S3 bucket.

```ymal
```shell
dumpling \
-u root \
-P 4000 \
Expand Down
2 changes: 1 addition & 1 deletion tidb-troubleshooting-map.md
Original file line number Diff line number Diff line change
Expand Up @@ -416,7 +416,7 @@ Check the specific cause for busy by viewing the monitor **Grafana** -> **TiKV**

- The binlog data is too large, so the single message written to Kafka is too large. You need to modify the following configuration of Kafka:

```conf
```properties
message.max.bytes=1073741824
replica.fetch.max.bytes=1073741824
fetch.message.max.bytes=1073741824
Expand Down
Loading