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

["Shubham Sharma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HAWQ-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394885#comment-16394885 ] 

Shubham Sharma commented on HAWQ-1530:
--------------------------------------

This issue is reproducible with 2.3.0.0 when multiple connections are opened using pgAdmin3(JDBC client). Also, another important part of reproducing this issue is that the communication between pgAdmin3 and hawq must be over network. If hawq and pgAdmin3 are present on same host the issue will not reproduce.

> 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: Yi Jin
>            Priority: Major
>             Fix For: 2.3.0.0-incubating
>
>
> 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
(v7.6.3#76005)