From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Performance Tuning |
Date: | 2006-02-18 02:59:45 |
Message-ID: | 87fymhtlr2.fsf@wolfe.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
The world rejoiced as ddelao(at)gmail(dot)com ("Darryl W. DeLao Jr.") wrote:
> Running ver 7.3.10 in RHEL 3.0 ES. If I change shared buffers, dont i have to change max connections as well?
If you have enough connections, then that seems unnecessary.
The *opposite* would be true; if you change max connections, you might
need to change the size of the shared buffer...
At any rate, if you actually want substantive improvements in
performance, I would *highly* advise moving to a version of PostgreSQL
that is *way* newer, like version 8.1. There are *enormous* numbers
of improvements that affect performance between 7.3 and 8.1.
--
output = reverse("gro.gultn" "@" "enworbbc")
http://cbbrowne.com/info/lsf.html
"In the case of CAPP, an EAL4 evaluation tells you everything you need
to know. It tells you that Microsoft spent millions of dollars
producing documentation that shows that Windows 2000 meets an
inadequate set of requirements, and that you can have reasonably
strong confidence that this is the case." -- Jonathan S. Shapiro
From | Date | Subject | |
---|---|---|---|
Next Message | Benjamin Smith | 2006-02-18 04:07:26 | Updating a sequential range of unique values? |
Previous Message | Christopher Browne | 2006-02-18 02:56:10 | Re: How do I use the backend APIs |