Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M52005=pgsql-performance-ar@postgresql.org>)
 id 1XBkhV-0005lm-LX
 for pgsql-performance@arkaria.postgresql.org; Mon, 28 Jul 2014 13:10:49 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-performance-owner+M52005=pgsql-performance-ar@postgresql.org>)
 id 1XBkhV-0001RG-1u
 for pgsql-performance@arkaria.postgresql.org; Mon, 28 Jul 2014 13:10:49 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <ruralhunter@gmail.com>)
 id 1XBkhT-0001Qb-T9; Mon, 28 Jul 2014 13:10:47 +0000
Received: from mail-pd0-x230.google.com ([2607:f8b0:400e:c02::230])
 by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <ruralhunter@gmail.com>)
 id 1XBkhM-0000fQ-4U; Mon, 28 Jul 2014 13:10:46 +0000
Received: by mail-pd0-f176.google.com with SMTP id y10so9872614pdj.21
 for <multiple recipients>; Mon, 28 Jul 2014 06:10:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=from:message-id:date:user-agent:mime-version:to:subject:references
 :in-reply-to:content-type:content-transfer-encoding;
 bh=ZiDMNnfCT0EbPHXEQf1RQr+20VZ1rkLtSRvLaNPvnC8=;
 b=FXnRZsi96g8s/zEuO4DOLMfpUZGqvo7zDYgZ6Mq647Y99/7JpCeYDSHS6zaAGFE1+O
 jsvlIQrkm+oUIAYQqGh1ltF9msXldbd2xUhbqfabRMnuB3O0VH8sxc08F3lNj5GJtSAx
 dC7luo/6+UPLbWdHRv+WIWqi8uyH2L9/yGnoTOQgfj/hzgZpR3KsMeYA3s+jeZk7ychD
 A1/y7LBb7oGtIAtE/xzNRdz8WahnVZRXnYM6mG3fgqQXSZo7+PcobYYOuRin2IuYhz5b
 nk7WrLrEoWKHywdVwaEVYVtUbMr5m6xHC2Q23/JFv2RHleFSm4BCKpFVgdImT6/OavXA
 5+Bw==
X-Received: by 10.70.131.35 with SMTP id oj3mr10095569pdb.116.1406553037181;
 Mon, 28 Jul 2014 06:10:37 -0700 (PDT)
Received: from [192.168.11.4] ([180.164.153.84])
 by mx.google.com with ESMTPSA id bc4sm17659285pbb.2.2014.07.28.06.10.34
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 28 Jul 2014 06:10:36 -0700 (PDT)
From: Rural Hunter <ruralhunter@gmail.com>
X-Google-Original-From: Rural Hunter <RuralHunter@gmail.com>
Message-ID: <53D64BC8.4020908@gmail.com>
Date: Mon, 28 Jul 2014 21:10:32 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.0
MIME-Version: 1.0
To: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>,
 "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Subject: Re: Very slow planning performance on partition table
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>
In-Reply-To: <24564.1406478487@sss.pgh.pa.us>
Content-Type: text/plain; charset=gb18030; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-performance>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-performance.postgresql.org>
List-Owner: <mailto:pgsql-performance-owner@postgresql.org>
List-Post: <mailto:pgsql-performance@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-performance>
List-Unsubscribe: 
 <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
X-Mailing-List: pgsql-performance
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

I am now seeing another phenominom of hanging connections. They are 
showing 'UPDATE' status in process list.
(gdb) bt
#0  0x00007f783f79d4f7 in semop () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00000000005f97d3 in PGSemaphoreLock ()
#2  0x0000000000638153 in LWLockAcquire ()
#3  0x00000000004a9239 in ginStepRight ()
#4  0x00000000004a9c61 in ginFindLeafPage ()
#5  0x00000000004a8377 in ginInsertItemPointers ()
#6  0x00000000004a4548 in ginEntryInsert ()
#7  0x00000000004ae687 in ginInsertCleanup ()
#8  0x00000000004af3d6 in ginHeapTupleFastInsert ()
#9  0x00000000004a4ab1 in gininsert ()
#10 0x0000000000709b15 in FunctionCall6Coll ()
#11 0x000000000047b6b7 in index_insert ()
#12 0x000000000057f475 in ExecInsertIndexTuples ()
#13 0x000000000058bf07 in ExecModifyTable ()
#14 0x00000000005766e3 in ExecProcNode ()
#15 0x0000000000575ad4 in standard_ExecutorRun ()
#16 0x000000000064718f in ProcessQuery ()
#17 0x00000000006473b7 in PortalRunMulti ()
#18 0x0000000000647e8a in PortalRun ()
#19 0x0000000000645160 in PostgresMain ()
#20 0x000000000060459e in ServerLoop ()
#21 0x00000000006053bc in PostmasterMain ()
#22 0x00000000005a686b in main ()
(gdb) q

This connection can not be killed by pg_cancel_backend nor 
pg_terminate_backend. It just hangs there and does not respond to normal 
kill command.  I had to kill -9 the process to terminate whole 
postgresql instance. What happened there and how can I kill these 
connections safely?


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