Skip to content
Merged
Changes from 4 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
1 change: 1 addition & 0 deletions releases/release-7.2.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,7 @@
### Behavior changes

- When processing update event, TiCDC splits an event into delete and insert events if the primary key or non-null unique index value is modified in the event. For more information, see [documentation](/ticdc/ticdc-split-update-behavior.md#transactions-containing-a-single-update-change).
- Changes the default value of [`tidb_remove_orderby_in_subquery`](/system-variables.md#tidb_remove_orderby_in_subquery-new-in-v610) from `OFF` to `ON`, meaning that the optimizer removes the `ORDER BY` clause in a subquery. This can avoid unnecessary sorting operations, which improves query performance in many cases. This change might result in a different order of query results. The ISO/IEC SQL standard does not require query results to follow the `ORDER BY` sorting of subqueries. To strictly guarantee the final result order, sorting must be explicitly included in the outer query. You can set this variable to `OFF` for applications that rely on subquery sorting. Clusters upgraded from earlier versions retain the previous behavior by default.

Check warning on line 176 in releases/release-7.2.0.md

View workflow job for this annotation

GitHub Actions / vale

[vale] reported by reviewdog 🐶 [PingCAP.Ambiguous] Consider using a clearer word than 'many' because it may cause confusion. Raw Output: {"message": "[PingCAP.Ambiguous] Consider using a clearer word than 'many' because it may cause confusion.", "location": {"path": "releases/release-7.2.0.md", "range": {"start": {"line": 176, "column": 309}}}, "severity": "INFO"}

### System variables

Expand Down
Loading