X-Original-To: pgsql-advocacy@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 9643D474E4F; Thu, 13 Feb 2003 12:11:04 -0500 (EST) Received: from candle.pha.pa.us (momjian.navpoint.com [207.106.42.251]) by postgresql.org (Postfix) with ESMTP id 38DF9474E42; Thu, 13 Feb 2003 12:11:03 -0500 (EST) Received: (from pgman@localhost) by candle.pha.pa.us (8.11.6/8.10.1) id h1DHAui22918; Thu, 13 Feb 2003 12:10:56 -0500 (EST) From: Bruce Momjian Message-Id: <200302131710.h1DHAui22918@candle.pha.pa.us> Subject: Re: [HACKERS] Changing the default configuration (was Re: In-Reply-To: <13183.1045148789@sss.pgh.pa.us> To: Tom Lane Date: Thu, 13 Feb 2003 12:10:56 -0500 (EST) Cc: Peter Eisentraut , Merlin Moncure , PostgresSQL Hackers Mailing List , pgsql-advocacy@postgresql.org X-Mailer: ELM [version 2.4ME+ PL99 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/63 X-Sequence-Number: 821 Tom Lane wrote: > Bruce Momjian writes: > > So, my idea is to add a message at the end of initdb that states people > > should run the pgtune script before running a production server. > > Do people read what initdb has to say? > > IIRC, the RPM install scripts hide initdb's output from the user > entirely. I wouldn't put much faith in such a message as having any > real effect on people... Yes, that is a problem. We could show something in the server logs if pg_tune hasn't been run. Not sure what else we can do, but it would give folks a one-stop thing to run to deal with performance configuration. We could prevent the postmaster from starting unless they run pg_tune or if they have modified postgresql.conf from the default. Of course, that's pretty drastic. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073