pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Rural Hunter <ruralhunter@gmail.com>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Very slow planning performance on partition table
Date: Mon, 04 Aug 2014 18:12:35 +0800
Message-ID: <53DF5C93.6010007@gmail.com> (raw)
In-Reply-To: <53D8C2F2.3080105@gmail.com>
References: <53CFB6BC.4050606@gmail.com>
	<25010.1406253203@sss.pgh.pa.us>
	<53D26875.2080604@gmail.com>
	<53D51E49.102@gmail.com>
	<24564.1406478487@sss.pgh.pa.us>
	<CAMkU=1ydmpt9XRMxt0sPNnQsXEoF_c7bgp2kHxtDbPNGg5Vj5w@mail.gmail.com>
	<53D7597E.2080209@gmail.com>
	<CAMkU=1wHC_w6D2kc1V6y1PDkRxDV3B+1fJBk3Z2L=SprGw7omw@mail.gmail.com>
	<53D8C2F2.3080105@gmail.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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.



-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (21+ messages)

Message-ID: <53DF5C93.6010007@gmail.com>
Permalink:  ../53DF5C93.6010007@gmail.com/
Also on:    postgresql.org/message-id/53DF5C93.6010007@gmail.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: ruralhunter@gmail.com
  Subject: Re: Very slow planning performance on partition table
  In-Reply-To: <53DF5C93.6010007@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox