Re: Huge spikes in number of connections doing "PARSE"

From: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Noah Misch <noah(at)leadboat(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Huge spikes in number of connections doing "PARSE"
Date: 2011-03-15 15:31:48
Message-ID: 20110315153147.GA30372@depesz.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Mar 15, 2011 at 10:58:52AM -0400, Tom Lane wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> > while I understand it, and will pass this information to client, one
> > thing bugs me - one the problem happens only sometimes, with relatively
> > low count of backends?
> > we saw database running normally with 1200 connections, yet sometimes,
> > it has 500 connections, and then something happens and they all end up
> > locking in this parse mode.
>
> Well, if they're all busy, you're not going to get this cache reset
> problem. It's idle backends that have fallen behind that create the
> problem.

thanks.

Best regards,

depesz

--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message MauMau 2011-03-15 15:46:52 test
Previous Message Manos Karpathiotakis 2011-03-15 15:28:10 Maximum number of tables