You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hawq.apache.org by "Grant Krieger (JIRA)" <ji...@apache.org> on 2017/09/25 09:13:00 UTC

[jira] [Created] (HAWQ-1530) Illegally killing a JDBC select query causes locking problems

Grant Krieger created HAWQ-1530:
-----------------------------------

             Summary: Illegally killing a JDBC select query causes locking problems
                 Key: HAWQ-1530
                 URL: https://issues.apache.org/jira/browse/HAWQ-1530
             Project: Apache HAWQ
          Issue Type: Bug
          Components: Transaction
            Reporter: Grant Krieger
            Assignee: Radar Lei


Hi,

When you perform a long running select statement on 2 hawq tables (join) from JDBC and illegally kill the JDBC client (CTRL ALT DEL) before completion of the query the 2 tables remained locked even when the query completes on the server. 

The lock is visible via PG_locks. One cannot kill the query via SELECT pg_terminate_backend(393937). The only way to get rid of it is to kill -9 from linux or restart hawq but this can kill other things as well.

The JDBC client I am using is Aqua Data Studio.

I can provide exact steps to reproduce if required

Thank you

Grant 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)