From: | "Darren King" <darrenk(at)insightdist(dot)com> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | RE: Re: Re: "--tuning" compile and runtime option (?) |
Date: | 2001-04-10 15:13:19 |
Message-ID: | NDBBJNEIGLIPLCHCMANLKEAICMAA.darrenk@insightdist.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I can't see how any configure option would be faster or
> better than the existing command line /config file parameters
> -- it would only serve to make things harder to deal with IMHO.
> "Tuning" PostgreSQL is pretty simple, and is explained pretty
> well throughout the manual (especially in the section titled
> "Understanding Performance"). We have -S -B and the fsync
> options, <Austin Powers Voice> That's about it.. </Austin Powers
> Voice> --- right?
> All are explained in the manual and are as easy to use as anyone could
> ask... Any OS tuning should be left up to the administrator
> as that's what administrators are for :-)
Someday, maybe other parameters (such as some of the optimizer's default
values) will be configurable/changable on the fly. Would seem silly to
have to stop/start the server to change those.
Just an example, I'm sure there are other internal values that admins
would like to tweak without recompiling or restarting. Would be much
nicer to login as the superuser to do it rather than shut down my site.
darrenk
From | Date | Subject | |
---|---|---|---|
Next Message | Mitch Vincent | 2001-04-10 15:26:02 | Re: Re: Re: "--tuning" compile and runtime option (?) |
Previous Message | Mitch Vincent | 2001-04-10 14:47:13 | Re: Re: "--tuning" compile and runtime option (?) |