From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
Cc: | "Guillaume Cottenceau" <gc(at)mnc(dot)ch>, "Matthew Wakeling" <matthew(at)flymine(dot)org>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: which ext3 fs type should I use for postgresql |
Date: | 2008-05-16 17:15:05 |
Message-ID: | 20080516101505.3e5814ed@jd-laptop |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Fri, 16 May 2008 11:07:17 -0600
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> wrote:
> Sorry, but that's like saying that open heart surgery isn't a fix for
> clogged arteries because you should have been taking aspirin everyday
> and exercising. It might not be the best answer, but sometimes it's
> the only answer you've got.
>
> I know that being able to drop the margin from x% to 0% for 10 minutes
> has pulled more than one db back from the brink for me (usually
> consulting on other people's databases, only once or so on my own) :)
My point is, if you are adjusting that parameter you probably have a
stray log or a bunch of rpms etc... that can be truncated to get
you where you need to be.
Of course there is always the last ditch effort of what you suggest but
first you should look for the more obvious possible solution.
Sincerely,
Joshua D. Drake
--
The PostgreSQL Company since 1997: http://www.commandprompt.com/
PostgreSQL Community Conference: http://www.postgresqlconference.org/
United States PostgreSQL Association: http://www.postgresql.us/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Ben | 2008-05-16 17:56:03 | very slow left join |
Previous Message | Scott Marlowe | 2008-05-16 17:07:17 | Re: which ext3 fs type should I use for postgresql |