Hi, Kindly see the below attached statements related to Cursor Fetch Issue it's still residing as a process. 500 20222 31036 79 Dec27 ? 16:22:31 postgres: user1 sampledb 192.168.0.40[36022] FETCH 500 20829 31036 81 Dec27 ? 16:18:48 postgres: user1 sampledb 192.168.0.40[57591] FETCH 500 20867 31036 81 Dec27 ? 16:09:33 postgres: user1 sampledb 192.168.0.40[45316] FETCH 500 20870 31036 81 Dec27 ? 16:09:12 postgres: user1 sampledb 192.168.0.40[45343] FETCH -- View this message in context: http://postgresql.1045698.n5.nabble.com/Cursor-fetch-Problem-tp5737915p5738099.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
