Well, what is being discussed here would require a *recompile* to change the
values, so you sure wouldn't want that! :-)
Currently you can set a lot of internal variables with the SET command in any PG
session.. It's useful for forcing index or sequential scans and such (and I'm
sure a lot more)..
-Mitch
Software development :
You can have it cheap, fast or working. Choose two.
----- Original Message -----
From: "Darren King" <darrenk@insightdist.com>
To: <pgsql-hackers@postgresql.org>
Sent: Tuesday, April 10, 2001 11:13 AM
Subject: RE: Re: Re: "--tuning" compile and runtime option (?)
> > 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
