X-Original-To: pgsql-advocacy@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id DA325475A45; Tue, 11 Feb 2003 12:06:02 -0500 (EST) Received: from snoopy.mohawksoft.com (h0030f1382639.ne.client2.attbi.com [24.60.194.163]) by postgresql.org (Postfix) with ESMTP id E65D5475843; Tue, 11 Feb 2003 12:06:01 -0500 (EST) Received: from mohawksoft.com (snoopy.mohawksoft.com [127.0.0.1]) by snoopy.mohawksoft.com (8.11.6/8.11.6) with ESMTP id h1BHC4a30725; Tue, 11 Feb 2003 12:12:05 -0500 Message-ID: <3E492EE4.1080502@mohawksoft.com> Date: Tue, 11 Feb 2003 12:12:04 -0500 From: mlw User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: Merlin Moncure , PostgresSQL Hackers Mailing List , pgsql-advocacy@postgresql.org Subject: Re: Changing the default configuration (was Re: References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <26004.1044980414@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------010600010708020705080102" X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/11 X-Sequence-Number: 769 --------------010600010708020705080102 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Tom Lane wrote: >"Merlin Moncure" writes: > > >>May I make a suggestion that maybe it is time to start thinking about >>tuning the default config file, IMHO its just a little bit too >>conservative, >> >> > >It's a lot too conservative. I've been thinking for awhile that we >should adjust the defaults. > > > One of the things I did on my Windows install was to have a number of default configuration files, postgresql.conf.small, postgresql.conf.medium, postgresql.conf.large. Rather than choose one, in the "initdb" script, ask for or determine the mount of shared memory, memory, etc. Another pet peeve I have is forcing the configuration files to be in the database directory. We had this argument in 7.1 days, and I submitted a patch that allowed a configuration file to be specified as a command line parameter. One of the things that Oracle does better is separating the "configuration" from the data. It is an easy patch to allow PostgreSQL to use a separate configuration directory, and specify the data directory within the configuration file (The way any logical application works), and, NO, symlinks are not a solution, they are a kludge. --------------010600010708020705080102 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit

Tom Lane wrote:
"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
  
May I make a suggestion that maybe it is time to start thinking about
tuning the default config file, IMHO its just a little bit too
conservative,
    

It's a lot too conservative.  I've been thinking for awhile that we
should adjust the defaults.

  
One of the things I did on my Windows install was to have a number of default configuration files, postgresql.conf.small, postgresql.conf.medium, postgresql.conf.large.

Rather than choose one, in the "initdb" script, ask for or determine the mount of shared memory, memory, etc.

Another pet peeve I have is forcing the configuration files to be in the database directory. We had this argument in 7.1 days, and I submitted a patch that allowed a configuration file to be specified as a command line parameter. One of the things that Oracle does better is separating the "configuration" from the data.

It is an easy patch to allow PostgreSQL to use a separate configuration directory, and specify the data directory within the configuration file (The way any logical application works), and, NO, symlinks are not a solution, they are a kludge.
--------------010600010708020705080102--