Re: Very slow planning performance on partition table

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-07-29 08:21:18
Message-ID: 53D7597E.2080209@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin pgsql-performance

More information found. After the hang connection appears, I noticed
there were several hundreds of connections of the same user. Since I use
pgbouncer and I only set the pool size to 50 for each user, this is very
strange. I checked the pgbouncer side, 'show pools' showed the active
server connection count is less than 50(only 35 actually). I also
checked the client port which is shown in pg process list. It is not
used at pgbouncer side when I did the check. So I stopped pgbouncer then
the connection count from the user drops slowly. Finally all those
connections disappeared. After that I restarted pgbouncer and it looks
good again.
With this solution, I at least don't have to kill pg when the problem
happens. But anyone has a clue why this happens? What I need to check
for the root cause? One thing I forgot to check is the network status of
those orphan connections at pg side. I will check it next time and see
if they are in abnormal status.

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jeff Janes 2014-07-29 17:27:11 Re: Very slow planning performance on partition table
Previous Message Cliff Pratt 2014-07-29 00:12:53 Re: I: "ERROR: could not access status of transaction" (after upgrding from 9.3.2 to 9.3.4?)

Browse pgsql-performance by date

  From Date Subject
Next Message Jiří Nádvorník 2014-07-29 09:44:46 Re: Cursor + upsert (astronomical data)
Previous Message Rural Hunter 2014-07-29 00:10:35 Re: Very slow planning performance on partition table