| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | "Thiyagarajan, Palaniappan" <pthiyagarajan(at)cashedge(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: PsqL8.3 |
| Date: | 2013-04-12 10:02:02 |
| Message-ID: | 5167DB9A.2070206@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 11/04/13 22:09, Thiyagarajan, Palaniappan wrote:
> All,
>
> We have performance issue in Psql8.3 vacuum run. The CPU usage going
> 300+ and application getting slow. How do we avoid high cpu and
> smooth vacuum tables.
I'm afraid this isn't nearly enough information for anyone to help.
1. Full version details, some idea of hardware and database size might
be useful. Exactly when this happens etc.
2. Is this a manual vacuum or autovacuum?
3. Are you familiar with the manual page regarding the vacuum settings?
http://www.postgresql.org/docs/8.3/static/runtime-config-autovacuum.html
4. If so, what changes have you made?
5. You are aware that 8.3 is end-of-life? And you are running 8.3.23
until you upgrade, aren't you?
http://www.postgresql.org/support/versioning/
Typically you'd expect disk i/o to be the limiting factor with vacuum
rather than CPU. However, it might just be that I've misunderstood your
description. More details please.
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rodrigo Barboza | 2013-04-12 16:45:07 | Segment best size |
| Previous Message | Jeff Janes | 2013-04-12 06:14:10 | Re: [PERFORM] Postgres log(pg_logs) have lots of message |