Mitu Verma wrote:
> I have killed the script, but still the query is showing in pg_stat and pg_locks.
>
> Please help me how to clear the pg_locks from the transaction it is already holding, if there is
> something in PostgreSQL which can clear the pg_stat and pg_locks?
[...]
> fm_db_Server3=# SELECT * FROM pg_stat_activity;
[...]
> 16384 | fm_db_Server3 | 28223 | 16391 | mmsuper | psql | |
> | -1 | 2015-04-22 11:39:12.384336+02 | 2015-04-22 11:39:33.36916+02 | 2015-04-22
> 11:39:33.36916+02 | t | delete from audittraillogentry where intime <= to_timestamp('2015-01-14
> 23:59:59.999', 'YYYY/MM/DD-HH24:MI:SS.FF3') OR outtime <= to_timestamp('2015-01-14 23:59:59.9
> 99', 'YYYY/MM/DD-HH24:MI:SS.FF3');
[...]
> 16384 | fm_db_Server3 | 3722 | 16391 | mmsuper | | 172.23.84.19 | s3bgwa31
> | 53620 | 2015-04-14 13:36:29.193159+02 | 2015-04-14 13:36:29.204018+02 | 2015-04-14
> 13:36:29.204018+02 | f | delete from audittraillogentry where intime <= to_timestamp('2015-01-14
> 23:59:59.999', 'YYYY/MM/DD-HH24:MI:SS.FF3') OR outtime <= to_timestamp('2015-01-14 23:59:59.9
> 99', 'YYYY/MM/DD-HH24:MI:SS.FF3')
You killed the script, but you did not cancel the queries.
Maybe you should change the script so that it cancels the queries when it is killed.
To get rid of the database sessions, do the following as superuser (because you are on 9.1):
SELECT pg_terminate_backend(28223);
SELECT pg_terminate_backend(3722);
Yours,
Laurenz Albe