Sean Chittenden [EMAIL PROTECTED] writes:
If you CLUSTER on an index and then ANALYSE, you get a correlation of
1.0 (== optimum) for the first column of the index.
Correlating of what to what? Of data to nearby data? Of data to
related data (ie, multi-column index?)? Of related data to
is some other problem that needs to be solved. (I'd wonder about
index correlation myself; we know that that equation is pretty
bogus.)
Could be. I had him create a multi-column index on the date and a
non-unique highly redundant id.
Tom has already suspected index correlation to be
Michael Pohl wrote:
On Sun, 6 Jul 2003, Matthew Nuzum wrote:
At the very least, if there is good documentation for these parameters,
maybe the conf file should provide a link to this info.
I believe that is what Josh is proposing:
Are you willing to say that the PostgreSQL database system should only be
used by DBAs? I believe that Postgres is such a good and useful tool that
anyone should be able to start using it with little or no barrier to entry.
I quite agree. But there is a difference between saying you should get
On Wed, 9 Jul 2003, Kaarel wrote:
Are you willing to say that the PostgreSQL database system should only be
used by DBAs? I believe that Postgres is such a good and useful tool that
anyone should be able to start using it with little or no barrier to entry.
I quite agree. But there
Scott Marlowe wrote:
It would be nice to have a program that could run on any OS postgresql
runs on and could report on the current limits of the kernel, and make
recommendations for changes the admin might want to make.
One could probably make a good stab at effective cache size during
I don't have much to add because I'm pretty new to Postgres and have
been soliciting advice here recently, but I totally agree with
everything you said. I don't mind if it's in the postgres.conf file
or in a faq that is easy to find, I just would like it to be in one
place. A good example
Sean Chittenden wrote:
I looked through the src/doc/runtime.sgml for a good place to stick
this and couldn't find a place that this seemed appropriate, but on
FreeBSD, this can be determined with a great deal of precision in a
programmatic manner:
echo effective_cache_size = $((`sysctl -n
Matthew Nuzum wrote:
I'm highly resistant to/disappointed in this attitude and firmly
believe that there are well understood algorithms that DBAs use to
diagnose and solve performance problems. It's only a black art
because it hasn't been documented. Performance tuning isn't voodoo,
it's
Brian Suggests:
I'm curious how many of the configuration values can be determined
automatically, or with the help of some script. It seem like there
could be some perl script in contrib that could help figure this out.
Possibly you are asked a bunch of questions and then the values
On Sun, 6 Jul 2003, Matthew Nuzum wrote:
At the very least, if there is good documentation for these parameters,
maybe the conf file should provide a link to this info.
I believe that is what Josh is proposing:
http://archives.postgresql.org/pgsql-performance/2003-07/msg00102.php
[Apache
Michael Pohl wrote:
On Sun, 6 Jul 2003, Matthew Nuzum wrote:
At the very least, if there is good documentation for these parameters,
maybe the conf file should provide a link to this info.
I believe that is what Josh is proposing:
On Thu, 3 Jul 2003, Sean Chittenden wrote:
What are the odds of going through and revamping some of the tunables
in postgresql.conf for the 7.4 release? I was just working with
someone on IRC and on their 7800 RPM IDE drives, their
random_page_cost was ideally suited to be 0.32: a far cry
13 matches
Mail list logo
