From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
---|---|
To: | ARTEAGA Jose <Jose(dot)Arteaga(at)alcatel-lucent(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Richard Huxton <dev(at)archonet(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Limitations on 7.0.3? |
Date: | 2007-06-08 18:58:26 |
Message-ID: | 4669A6D2.60507@g2switchworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
ARTEAGA Jose wrote:
> Also worth mentioning is that I just this week found out about a very,
> very important parameter "shared buffers". Ever since the original
> person setup our PG (individual no longer with us) this DB had been
> running without any major glitches, albeit slow. All this time the
> shared buffers were running at default of "64" (8192 block size). Once I
> have got this back up and running I have since set this to 1600 shared
> buffers (~125MB). I've since noticed a dramatic performance improvement,
> I hope that I've striked gold. But cannot claim victory yet it's only
> been up for 2 days.
If you think increasing shared buffers in 7.0 improves things, you
should see what upgrading to 8.2.4 will do.
Seriously, you'll freak at the increase in speed.
7.0 = handcar: http://www.handcar.net/
8.2 = TGV: http://en.wikipedia.org/wiki/TGV
(p.s. please upgrade before 7.0 eats your data...)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2007-06-08 19:00:35 | Re: Wider than float8 |
Previous Message | MC Moisei | 2007-06-08 18:23:00 | Postmaster processes taking all the CPU |