From: | Bill Moran <wmoran(at)potentialtech(dot)com> |
---|---|
To: | "Preeti Khurana" <preeti(dot)khurana(at)globallogic(dot)com> |
Cc: | Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Postgres's Performance degrades after heavy db operation |
Date: | 2009-06-10 12:14:30 |
Message-ID: | 20090610081430.f15616ac.wmoran@potentialtech.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In response to "Preeti Khurana" <preeti(dot)khurana(at)globallogic(dot)com>:
> I checked the release notes till 8.1.17, but could not come across any such issue which leads to db performance degradation after doing heavy db operations.
I don't think that was his point. I expect it was something more along the
lines of crashing bugs and data corruption bugs that you might want to
have fixed.
> AutoVacuum is also enabled parallel.
Which means virtually nothing if we're trying to help you tune. What are
your autovacuum settings? Simply turning it on is not always enough (if
it were, there wouldn't be a need to have other settings, now would there)
And I'll reiterate something that was said on this thread earlier ... it's
likely that autovacuum isn't going to be enough for your usage pattern.
Have you posted the output of VACUUM VERBOSE yet?
--
Bill Moran
http://www.potentialtech.com
http://people.collaborativefusion.com/~wmoran/
From | Date | Subject | |
---|---|---|---|
Next Message | Jasen Betts | 2009-06-10 12:19:55 | Re: limit table to one row |
Previous Message | Pedro Doria Meunier | 2009-06-10 10:26:54 | Average connections |