Re: [GENERAL] Cursor fetch Problem.

2012-12-30 Thread Amit kapila
On Friday, December 28, 2012 10:58 AM Harry wrote: > 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 Dec2

Re: [GENERAL] Cursor fetch Problem.

2012-12-28 Thread Harry
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[5759

Re: [GENERAL] Cursor fetch Problem.

2012-12-28 Thread Harry
No any statements as u mentioned. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Cursor-fetch-Problem-tp5737915p5738120.html Sent from the PostgreSQL - general mailing list archive at Nabble.com. -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org)

Re: [GENERAL] Cursor fetch Problem.

2012-12-28 Thread Amit Kapila
On Thursday, December 27, 2012 2:44 PM Harry wrote: > Below is the Linux ps -ef | grep postgres output :- > > 501 12163 5473 0 Dec19 ?00:00:00 postgres: enterprisedb > sampledb 192.168.0.231[53991] ?EDB-SPL Procedure successfully completed > 501 12167 5473 0 Dec19 ?00

Re: [GENERAL] Cursor fetch Problem.

2012-12-27 Thread Harry
Below is the Linux ps -ef | grep postgres output :- 501 12163 5473 0 Dec19 ?00:00:00 postgres: enterprisedb sampledb 192.168.0.231[53991] ?EDB-SPL Procedure successfully completed 501 12167 5473 0 Dec19 ?00:00:00 postgres: enterprisedb sampledb 192.168.0.231[53995] ?E

Re: [GENERAL] Cursor fetch Problem.

2012-12-27 Thread Amit Kapila
On Thursday, December 27, 2012 11:51 AM Harry wrote: > Hi Amit, > Thanks for Reply. > Kindly see my below output. > > 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). Can you

Re: [GENERAL] Cursor fetch Problem.

2012-12-27 Thread Amit Kapila
On Thursday, December 27, 2012 11:51 AM Harry wrote: > 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*";

Re: [GENERAL] Cursor fetch Problem.

2012-12-26 Thread Harry
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";"";"

Re: [GENERAL] Cursor fetch Problem.

2012-12-26 Thread Amit Kapila
On Wednesday, December 26, 2012 5:12 PM Harry wrote: > Hi All, > > I am getting a problem i.e. in database while checking pg_stat_activity > faced issue statement is residing as > process > for couple of days also, How have you concluded, it stays for couple of days? pg_stat_activity will show

[GENERAL] Cursor fetch Problem.

2012-12-26 Thread Harry
Hi All, I am getting a problem i.e. in database while checking pg_stat_activity faced issue statement is residing as process for couple of days also, not able to kill them through pg_terminate_backend function. -- View this message in context: http://postgresql.1045698.n5.nabble.com/Cursor-