You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@shardingsphere.apache.org by GitBox <gi...@apache.org> on 2021/08/02 07:37:57 UTC

[GitHub] [shardingsphere] JiekerTime opened a new issue #11599: Significant speed difference between executeUpdate and execute

JiekerTime opened a new issue #11599:
URL: https://github.com/apache/shardingsphere/issues/11599


   ### Which version of ShardingSphere did you use?
   5.0.0-RC1-SNAPSHOT
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   ShardingSphere-Proxy
   
   ### Expected behavior
   ![image](https://user-images.githubusercontent.com/76552510/127821874-2afd3fd0-bcb2-4f88-bf37-d23e8e180957.png)
   
   ### Actual behavior
   The test fails unless I add the following logic：
   ![image](https://user-images.githubusercontent.com/76552510/127821973-88596b34-c35a-4ced-a085-e388d8da9fa8.png)
   ![image](https://user-images.githubusercontent.com/76552510/127822049-db26e80f-d630-42f1-b380-2e523bf31687.png)
   
   ### Reason analyze (If you can)
   There seems to be a significant speed difference between executeUpdate and execute when DDL operations are in PG scenarios.
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
   Turn on the test as follows
   ![image](https://user-images.githubusercontent.com/76552510/127822123-91146748-9a4c-4c66-b562-a189cffb9cda.png)
   


-- 
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-unsubscribe@shardingsphere.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org