From: Rural Hunter <ruralhunter@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
To: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Very slow planning performance on partition table
Date: Mon, 28 Jul 2014 21:10:32 +0800
Message-ID: <53D64BC8.4020908@gmail.com> (raw)
In-Reply-To: <24564.1406478487@sss.pgh.pa.us>
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>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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
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, pgsql-admin@postgresql.org
Subject: Re: Very slow planning performance on partition table
In-Reply-To: <53D64BC8.4020908@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