From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Justin Clift <jclift(at)iprimus(dot)com(dot)au> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: "--tuning" compile and runtime option (?) |
Date: | 2001-04-09 16:28:53 |
Message-ID: | Pine.LNX.4.30.0104091822470.1255-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Justin Clift writes:
> When we get around to PostgreSQL's self-tuning ability being actively
> developed (and I think Bruce has done some of the very start with his
> monitor program), perhaps having a compile time option to set the
> default for the server, and a runtime option in case it changes?
> i.e.
> --tuning=superserver
> --tuning=shared
> --tuning=embedded
> postmaster -t superserver
> postmaster -t shared
> postmaster -t embedded
I'm generally no friend of generic "make it fast", "make it small"
options. It is usually hard to decide what settings should go under what
heading because everyone is in a different situation. The solution is to
provide user guidance to the existing configuration variables that goes
beyond what they do by adding why the user should care.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2001-04-09 16:44:47 | Re: RPMS for RC3 |
Previous Message | Peter Eisentraut | 2001-04-09 16:18:37 | Re: AW: RPM upgrade caveats going from a beta version to RC |