pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Greg Smith <greg@2ndquadrant.com>
To: David Rees <drees76@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Occasional giant spikes in CPU load
Date: Thu, 08 Apr 2010 02:08:05 -0400
Message-ID: <4BBD72C5.8060204@2ndquadrant.com> (raw)
In-Reply-To: <y2r72dbd3151004071556j22244233l8fa1db295b7f9cd3@mail.gmail.com>
References: <k2pda0294261004061437p9cd3810dqe9ce528b6ddb0873@mail.gmail.com>
	<m2m603c8f071004071413w1f2d2497hbbe07d9c6491848f@mail.gmail.com>
	<4BBCFB12.1010306@emolecules.com>
	<y2r72dbd3151004071556j22244233l8fa1db295b7f9cd3@mail.gmail.com>

David Rees wrote:
> You need to find out what all those Postgres processes are doing.  You
> might try enabling update_process_title and then using ps to figure
> out what each instance is using.

That's what the addition of "-c" to top I suggested does on Linux; it 
shows the updated process titles where the command line is in the 
default config.

-- 
Greg Smith  2ndQuadrant US  Baltimore, MD
PostgreSQL Training, Services and Support
greg@2ndQuadrant.com   www.2ndQuadrant.us

view thread (31+ messages)  latest in thread

Message-ID: <4BBD72C5.8060204@2ndquadrant.com>
Permalink:  ../4BBD72C5.8060204@2ndquadrant.com/
Also on:    postgresql.org/message-id/4BBD72C5.8060204@2ndquadrant.com

copy link · copy postgr.es

reply

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: greg@2ndquadrant.com, drees76@gmail.com
  Subject: Re: Occasional giant spikes in CPU load
  In-Reply-To: <4BBD72C5.8060204@2ndquadrant.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