sandynz opened a new issue, #17409: URL: https://github.com/apache/shardingsphere/issues/17409
## Bug Report ### Which version of ShardingSphere did you use? master branch, commit d7a8079e5141474e47e4aaa42221feda32047964 ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? Proxy ### Expected behavior gsql could login to Proxy with postgres. ### Actual behavior Client log: ``` omm@b74ff82d07b4:~$ gsql --host=host.docker.internal --port=3307 postgres root Password for user root: Failed to get the server's version. resStatus=7 ERROR: ERROR: org.apache.shardingsphere.proxy.backend.exception.RuleNotExistedException ``` No log in Proxy. ### Reason analyze (If you can) `postgres` exists in registry center `/metadata/postgres/`, though content is empty. The error occur when executing `SELECT VERSION()`. <img width="1377" alt="图片" src="https://user-images.githubusercontent.com/42492540/167236466-614d25dd-7d87-4f09-bad1-59c58bc53831.png"> Similar situation works on PostgreSQL backend. ``` % psql --host=localhost --port=3307 postgres root Password for user root: psql (13.4, server 12.3-ShardingSphere-Proxy 5.1.2-SNAPSHOT-371f15e) Type "help" for help. ``` Seems after authentication, there's no more query SQL with psql. No sure what's wrong with gsql. ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. 1, Install MogDB v2.1, refer to https://docs.mogdb.io/zh/mogdb/v2.1/docker-installation . Or try openGauss 2, Update `server.yaml`: Add ``` proxy-frontend-database-protocol-type: openGauss ``` in `props`. 3, Start Proxy. 4, Login with gsql ``` docker exec -it mogdb bash su - omm gsql --host=host.docker.internal --port=3307 postgres root ``` ### 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
