Re: Moving postgresql.conf tunables into 2003...

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
> install. Anything reasonably close would probably help.
>
> Report what % of said resources could be consumed by postgresql under
> various circumstances...
>

One of the issues that automating the process would encounter are limits
in the kernel that are too low for PostgreSQL to handle. The BSD's come
to mind where they need values manually increased in the kernel before
you can reach a reasonable maximum connection count.

Another example is how OpenBSD will outright crash when trying to test
the database during install time. It seems that most of the tests fail
because the maximum amount of processes allowed is too low for the test
to succeed. While FreeBSD will work just fine on those same tests.

If PostgreSQL automates the configuration, that would be a plus. But
also detect the platform and inform the person that these changes should
be done to the kernel, sysctl or whatever in order to have that
configuration run.

Perl may be useful in this for a few reasons. It's portable enough to
run on multiple Unix variants and the tools would be fairly standard, so
the code would require less considerations for more exotic implementations.

Martin Foster
Creator/Designer Ethereal Realms
martin(at)ethereal-realms(dot)org