Chris

There is no difference to the plugin in how it creates the connection to the database - the only thing different would be which database it's connecting to. When you...

without more details, hard to say - there's probably a connection issue with either incorrect credentials or there might be something configured on the server side to prevent the connection...

this would likely be due to the fact the the extension does not keep a persistent connection to the database open. that was a design decision to allow maintenance on...

This likely has to do with your theme. The background color of the results view is this: ```css background-color: var(--vscode-editor-background, var(--theme-background)); ``` and the cell border colors are this: ```css...

While not exactly the same, I think this is related to #196 and as a consequence a result to an upgrade with the related issue in vscode (https://github.com/microsoft/vscode/issues/147515) That error...

I can understand the benefit of a continuous session, and the overhead it takes to establish the new connections. During the initial design I gave some thought to this but...

While I agree it's weird... that error is coming direct from a Postgres server, and not generated by this plugin. For each of those scenarios, what does the vscode status...

So... I just tested this and was not able to replicate. Testing process: Created and saved a `.pgsql` file with a simple select query in it, tested it (while saved)...

while the error is definitely coming _from_ postgres, what might help is screenshots of the status bar - specifically the postgres server and the selected language of the saved file:...

I get the need to obscure or hide sensitive information - but unfortunately this is actually a postgres issue (postgres is reporting the error) - comparing that information to rules...