The execution plan of SQL in DBeaver is inconsistent with the execution plan generated after calling the interface in Postman

Translated
1

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: DBeaver里执行的sql计划和postman调用接口后生成的执行计划不一致

| username: jboracle1981

【TiDB Usage Environment】Production Environment
【TiDB Version】V7.1.2
【Reproduction Path】What operations were performed when the issue occurred
【Encountered Issue: Problem Phenomenon and Impact】The execution plan of the SQL executed in DBeaver is inconsistent with the execution plan generated after calling the interface via Postman. Has anyone encountered this?
【Resource Configuration】Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
【Attachments: Screenshots/Logs/Monitoring】

2
| username: jboracle1981 | Original post link

Has anyone encountered this problem?
The page or Postman calls are very slow, but DBeaver executes very quickly. The same statement generates different execution plans with different tools.