You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Attach "postgres" database with connection string?ssl=true.
Check whether no error occurs after attaching "postgres" database.
Expect:
No error occurs after attaching "postgres" database.
Actual:
An error occurs after attaching "postgres" database.
More Info:
There is an extra single quote in the Connect String. No error occurs after deleting the single quotes, such as: error connection string: postgres://cindy%40cindy-single:'Tcd...815615'@cindy-single.postgres.database.azure.com:5432/postgres correct connection string: postgres://cindy%40cindy-single:Tcd...815615@cindy-single.postgres.database.azure.com:5432/postgres
The text was updated successfully, but these errors were encountered:
Verified this issue on the extension build 20230911.4, another error occurs when attaching PostgreSQL server with the copied connection string.
The extra single quote still shows in the copied Connect String. Delete the extra single quote and add "?ssl=true" to the connection string, the error disappears.
OS: Win10
Build Version: 20221220.1
Repro Steps:
connection string?ssl=true
.Expect:

No error occurs after attaching "postgres" database.
Actual:

An error occurs after attaching "postgres" database.
More Info:
There is an extra single quote in the Connect String. No error occurs after deleting the single quotes, such as:
error connection string: postgres://cindy%40cindy-single:'Tcd...815615'@cindy-single.postgres.database.azure.com:5432/postgres
correct connection string: postgres://cindy%40cindy-single:Tcd...815615@cindy-single.postgres.database.azure.com:5432/postgres
The text was updated successfully, but these errors were encountered: