Re: Postmaster hogs CPU - Mailing list pgsql-admin

From Chris Gamache
Subject Re: Postmaster hogs CPU
Date
Msg-id 20040506160133.54511.qmail@web13808.mail.yahoo.com
Whole thread Raw
In response to Re: Postmaster hogs CPU  ("scott.marlowe" <scott.marlowe@ihs.com>)
List pgsql-admin
--- "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

pgsql-admin by date:

Previous
From: "scott.marlowe"
Date:
Subject: Re: Postmaster hogs CPU
Next
From: Martin Brommer
Date:
Subject: Meta data corruption