FlyingZC opened a new issue, #22493: URL: https://github.com/apache/shardingsphere/issues/22493
## Bug Report **For English only**, other languages will not accept. Before report a bug, make sure you have: - Searched open and closed [GitHub issues](https://github.com/apache/shardingsphere/issues). - Read documentation: [ShardingSphere Doc](https://shardingsphere.apache.org/document/current/en/overview). Please pay attention on issues you submitted, because we maybe need more details. If no response anymore and we cannot reproduce it on current information, we will **close it**. Please answer these questions before submitting your issue. Thanks! ### Which version of ShardingSphere did you use? master ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? proxy ### Expected behavior Can't execute `set transaction isolation level serializable;` in proxy. ```sql -- set serializable isolation sharding_db=> set transaction isolation level serializable; SET -- but not success sharding_db=> show transaction_isolation; transaction_isolation ----------------------- read committed (1 row) ``` ### Actual behavior Can execute `set transaction isolation level serializable;` success in proxy and take effect. ### Reason analyze (If you can) `PostgreSQLTCLStatementSQLVisitor` is not parsing this sql. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. Refer to this class `MySQLTCLStatementSQLVisitor`, add the similar logic for postgresql. ### Example codes for reproduce this issue (such as a github link). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@shardingsphere.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
