Hi Amit, Thanks for Reply. Kindly see my below output. 16650;"sampledb";11965;10;"enterprisedb";"";"192.168.0.231";"";53897;"*2012-12-19 11:39:48.234799+05:30";"2012-12-19 11:39:53.288441+05:30";"2012-12-19 11:39:53.288441+05:30*";f;"DECLARE BEGIN EXEC 16650;"sampledb";12156;10;"enterprisedb";"";"192.168.0.231";"";53983;*"2012-12-19 12:18:38.57709+05:30";"2012-12-19 12:18:43.922301+05:30";"2012-12-19 12:18:43.922301+05:30"*;f;"DECLARE BEGIN EXEC 16650;"sampledb";13243;10;"enterprisedb";"Postgres Studio - Browser";"192.168.0.180";"";3907;"2012-12-26 16:35:45.753172+05:30";"";"2012-12-26 16:35:46.577723+05:30";f;"<IDLE>" Also, tried to Kill it Firstly by using Cancel Backend and then Terminate Backend output showing "True" but still remaining as a process (i.e. in pg_stat_activity). -- View this message in context: http://postgresql.1045698.n5.nabble.com/Cursor-fetch-Problem-tp5737915p5737995.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
