Horton

Re: [HACKERS] Changing the default configuration (was Re:

Bruce Momjian <pgman@candle.pha.pa.us>

View thread View on postgr.es
From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>, Merlin Moncure <merlin.moncure@rcsonline.com>, PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>, pgsql-advocacy@postgresql.org
Date: 2003-02-13T17:10:56Z
Lists: pgsql-hackers, pgsql-performance 
Tom Lane wrote:
> Bruce Momjian <pgman@candle.pha.pa.us> 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