| From: | Rural Hunter <ruralhunter(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Very slow planning performance on partition table |
| Date: | 2014-08-04 10:12:35 |
| Message-ID: | 53DF5C93.6010007@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-performance |
在 2014/7/30 18:03, Rural Hunter 写道:
> I think I understand what happened now. I have another monitor script
> runs periodically and calls pg_cancel_backend and pg_terminate_backend
> for those hanging update sqls. However for some unkown reason the
> cancle and termiante command doesn't work at pgsql side for those
> update sqls.
>
With the log of the monitor&kill scipt, I can confirm that the
CLOSE_WAIT is not caused by it. I logged the netstat before actually
doing the kill and found the CLOSE_WAIT connections were already there.
So it must be something else caused the CLOSE_WAIT connections.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Khangelani Gama | 2014-08-04 10:34:52 | upgrading postgres 7.3.4 to 9.1.9 |
| Previous Message | Albe Laurenz | 2014-08-04 07:35:52 | Re: PITR WAL Restore and configuration |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Joseph Krogh | 2014-08-05 21:38:08 | Query performing very bad and sometimes good |
| Previous Message | Rural Hunter | 2014-08-04 07:23:11 | Re: Very slow planning performance on partition table |