pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Gamache <cgg007@yahoo.com>
To: scott.marlowe <scott.marlowe@ihs.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postmaster hogs CPU
Date: Thu, 6 May 2004 09:01:33 -0700 (PDT)
Message-ID: <20040506160133.54511.qmail@web13808.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0405051524160.3214-100000@css120.ihs.com>

--- "scott.marlowe" <scott.marlowe@ihs.com> wrote:
> On Wed, 5 May 2004, Chris Gamache wrote:
 
> Have you read:
> 
> http://www.varlena.com/varlena/GeneralBits/Tidbits/perf.html
> 
> yet?  It may just be that you don't have enough shared_buffers or whatnot.

Absolutely. I have a copy on my desk, and one under my pillow at night. :)
PostgreSQL profiling is a bit of an art. I've been a settings-tweaker since I
can remember. I feel like my config is pretty well balanced. Its that giant,
oddball-query that throws the proverbial wrench in the gears. The guide is
quick to warn that "too much" in any particular setting can be as bad as "not
enough" ... That's not to say that someone else, with more expertise than I,
couldn't look at what I have as far as settings and choose some better ones. 

The query_priority idea sounds like a promising idea. For queries that you
/know/ will be expensive (or that you know you want to have run lickety-split),
it'd do the trick. The next logical step would be an "intelligent" query
priority engine. However, that might require some ESP (the X-Files kind) ...
How do the other big RDBMS's do it?

CG


	
		
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover 



view thread (7+ messages)

Message-ID: <20040506160133.54511.qmail@web13808.mail.yahoo.com>
Permalink:  ../20040506160133.54511.qmail@web13808.mail.yahoo.com/
Also on:    postgresql.org/message-id/20040506160133.54511.qmail@web13808.mail.yahoo.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cgg007@yahoo.com, scott.marlowe@ihs.com
  Subject: Re: Postmaster hogs CPU
  In-Reply-To: <20040506160133.54511.qmail@web13808.mail.yahoo.com>
  References: <Pine.LNX.4.33.0405051524160.3214-100000@css120.ihs.com> <20040506160133.54511.qmail@web13808.mail.yahoo.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