Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Mar 14, 2011 at 10:21:27PM +0100, Martijn van Oosterhout wrote:
> On Mon, Mar 14, 2011 at 07:49:46PM +0100, hubert depesz lubaczewski wrote:
> > These 60 were summarized, and output is available here:
> > http://www.depesz.com/various/locks.summary.txt
> > 
> > as you can seem, in 48 cases backend process was in semop(), which relates
> > directly to my previous findings with ps/wchan.
> 
> It's unfortunate you don't have debug symbols enabled, which makes
> these traces somewhat unreliable. So you get odd things like index_open
> calling index_close.

That trace is legitimate.  If index_open()'s call into the relcache needs to
consult the catalogs, it will in turn scan pg_class_oid_index.

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


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux