Skip to content

upgrade: replace the wrong command SELECT TIDB_CURRENT_TSO() with BEGIN; SELECT TIDB_CURRENT_TSO(); ROLLBACK; (#22203) #22206

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.

Sign up for GitHub

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

Merged
ti-chi-bot merged 1 commit into from
Dec 18, 2025
Merged

upgrade: replace the wrong command SELECT TIDB_CURRENT_TSO() with BEGIN; SELECT TIDB_CURRENT_TSO(); ROLLBACK; (#22203) #22206

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions tidb-upgrade-migration-guide.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -222,7 +222,7 @@ Additionally, you can scale out the new cluster to handle expected workloads and
- After setting the old cluster to read-only mode, retrieve the current `up-tso`:

```sql
SELECT tidb_current_ts();
BEGIN; SELECT TIDB_CURRENT_TSO(); ROLLBACK;
```

- Monitor the Changefeed `checkpointTs` to confirm it has surpassed `up-tso`, indicating that TiCDC has completed data replication.
Expand Down Expand Up @@ -268,7 +268,7 @@ Additionally, you can scale out the new cluster to handle expected workloads and
2. Record the current TSO of the new cluster:

```sql
SELECT tidb_current_ts();
BEGIN; SELECT TIDB_CURRENT_TSO(); ROLLBACK;
```

3. Configure the reverse replication link and ensure the Changefeed task is running properly:
Expand Down