| From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
|---|---|
| To: | "'Harry'" <shirlekar(dot)harshal(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Cursor fetch Problem. |
| Date: | 2012-12-27 06:09:59 |
| Message-ID: | 000901cde3f8$cdb2bcd0$69183670$@kapila@huawei.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 <Fetch all in unnamed portal> is residing as
> process
> for couple of days also,
How have you concluded, it stays for couple of days?
pg_stat_activity will show last statement executed in backend. What is the
value of 'state' for that backend.
It's better if you can send the output of pg_stat_activity for that backend.
> not able to kill them through pg_terminate_backend function.
Can you try once pg_cancel_backend(pid) and then pg_terminate_backend.
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Harry | 2012-12-27 06:20:38 | Re: Cursor fetch Problem. |
| Previous Message | Bexley Hall | 2012-12-26 22:34:17 | Re: New Zealand Postgis DBA job vacancy |