[PostgreSQL] Query aborting waits end of execution
See original GitHub issueSystem information:
- Windows 7 Pro x64
- DBeaver 6.3.4.202002011957, 6.3.5.202002081854 (EA)
- No additional extensions
Connection specification:
- PostgreSQL 9.3
- PostgreSQL default driver (9.4.1212.jre7)
- No tunnels or proxies
Describe the problem you’re observing:
Query aborting waits end of execution
Steps to reproduce, if exist:
Execute SELECT pg_sleep(20)
and try to cancel it. It will be canceled after 20 sec, not immediately (after end of query execution)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Is a Postgres long-running query aborted if the connection is ...
As far as PostgreSQL is concerned if the client goes away its job is to terminate any queries the client was running.
Read more >current transaction is aborted, commands ignored until end of ...
The reason you get this error is because you have entered a transaction and one of your SQL Queries failed, and you gobbled...
Read more >How to Find and Stop Running Queries on PostgreSQL
Stopping Queries via SQL in Two Steps · 1. Find the pid · 2. Terminate, or Cancel, the Process.
Read more >Documentation: 15: 55.2. Message Flow - PostgreSQL
In the event of an error, ErrorResponse is issued followed by ReadyForQuery. All further processing of the query string is aborted by ErrorResponse...
Read more >Documentation: 15: 34.5. Pipeline Mode - PostgreSQL
libpq pipeline mode allows applications to send a query without having to read the ... in the pipeline immediately, not waiting for the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
verified
@kseniiaguzeeva In my case it was enough to leave program in an idle state for a few minutes (half hour maybe). Then an attempt of a statement execution runs infinitely.