Extension stops working after a while

[txomon]

• PGSQL Extension Version: 0.2.0
• VSCode Version: 1.33.0
• OS Version: Arch Linux

Steps to Reproduce:

1. Run queries for a while

After running queries for a while, the extension stops working and the only way to make it work again is by restarting the IDE.

The error is:

PostgreSQL: Execution failed: Another query is currently executing.

[akamath46297]

@txomon , could you please share exact repro steps to help us investigate this further. Are you experiencing this while executing any specific queries ?

From the message you pasted looks like there was some long running already under executing using a connection and you were trying to execute another query using the same connection. Did you try doing PostgreSQL: Cancel Query ?

[txomon]

Hello Anup, I clicked on the message down right that was popping, and for what I know there wasn't any query running (I was doing explain analyze performance inspection on some queries). I don't remember whether I canceled explicitly the query though. I will notify again if I can reproduce, and will post more explicitly about all the actions I took. Could I suggest that somehow we bring up visibility of what connections are open and what queries are running? This would be extremely helpful when debugging something like this. Cheers, Javier

…

On Sat, Apr 13, 2019 at 12:06 AM Anup N. Kamath ***@***.***> wrote: @txomon <https://github.com/txomon> , could you please share exact repro steps to help us investigate this further. Are you experiencing this while executing any specific queries ? From the message you pasted looks like there was some long running already under executing using a connection and you were trying to execute another query using the same connection. Did you try doing PostgreSQL: Cancel Query ? [image: image] <https://user-images.githubusercontent.com/30480046/56068598-46432980-5d34-11e9-8000-3e3fbedf0ac0.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAN7moTTrUzli9p64J9uYb45fSpbVVvrks5vgQNzgaJpZM4co5ya> .

-- Javier Domingo Cansino

[avradip]

Experiencing the same issue, is there any way to check which query is currently running?

[avradip]

Cancel query says 'Cannot cancel query as no query is currently running', Only way to get around the problem is closing and opening VScode.

[JimBreton]

Cancel query says 'Cannot cancel query as no query is currently running', Only way to get around the problem is closing and opening VScode.

For me, I can always get past it by doing a 'Reload Window' from the Command Palette. Still not great, but faster and easier than doing a full close/re-open. HTH.

[johny-numbers]

I get the same error message. When I Reload Window and reconnect, I get "the connection is already closed" and then back to "another query is currently executing". For me it happens without any discernable pattern of behaviour. I run a few simple select queries successfully, without canceling and start getting the error message. Sometimes I only get a single successful execution before the error comes up.

I'm running extension version 0.2.1 in Azure Data Studio 1.9.0 (VS Code 1.34.0) on Ubuntu 19.04.

[qiaohaojie]

Same issues here. And same issue also exists in Azure Data Studio.

PyCharm works perfectly. I have to go back to PyCharm for now.

[theogeer]

Same for me, Also in Azure Data Studio

[horns-k]

This is still happening in Azure Data Studio v 1.16.1

[daniloviterbo]

Still in ADS 1.17.1...

[driessamyn]

Also in 1.20.1

[horns-k]

Also in 1.20.1

Can confirm from our side as well. This is still happening with 1.20.1 after about 70-80 mins of application being idle.
Seems to be the case both for long running queries, and if not running queries for a while also.

[akshayjain9116]

Did we find any solution for this

[Brayozin]

any solution?