Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Changing the default configuration

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Daniel Kalchev <daniel(at)digsys(dot)bg>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>,pgsql-advocacy(at)postgresql(dot)org
Subject: Re: [HACKERS] Changing the default configuration
Date: 2003-02-13 19:22:18
Message-ID: 200302131922.h1DJMIT05304@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-advocacypgsql-hackers
I imagined they could run pgtune anytime after install to update those
performance parameters.  It gives them a one-stop location to at least
do minimal tuning, and as their load changes, they can run it again.

---------------------------------------------------------------------------

Daniel Kalchev wrote:
> >>>Bruce Momjian said:
> [...]
>  > For example, we can ask them how many rows and tables they will be
>  > changing, on average, between VACUUM runs.  That will allow us set the
>  > FSM params.  We can ask them about using 25% of their RAM for shared
>  > buffers.  If they have other major apps running on the server or have
>  > small tables, we can make no changes.  We can basically ask them
>  > questions and use that info to set values.
> 
> Bruce, this is an very good idea and such tool would simplify setup for the 
> me-too type of DBA - we should definitely try to attract them.
> 
> However, how could one possibly answer the above question, if they setup their 
> database for the first time?
> 
> What is more, these settings are on a per-installation, not per-database - 
> which means, that if you have several small, but active databases and one 
> large database the requirements will be very different.
> 
> Nobody likes answering such questions when installing new software. You might 
> enjoy it the first few times, but then learn the 'answers' and don't even 
> think what the question is. (we all know the answer :)
> 
> Perhaps indeed a better idea is to have PostgreSQL itself collect usage 
> statistics, and from time to time print 'suggestions' to the log file (best in 
> my opinion), or have these available via some query. These suggestions should 
> best reflect the of course require minimal intervention to the database 
> system, such as restart etc.
> 
> 
> Daniel
> 
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
> 
> http://archives.postgresql.org
> 

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman(at)candle(dot)pha(dot)pa(dot)us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

In response to

Responses

pgsql-hackers by date

Next:From: Robert TreatDate: 2003-02-13 19:23:38
Subject: Re: location of the configuration files
Previous:From: Andres LedesmaDate: 2003-02-13 19:21:50
Subject: Re: [ADMIN] help me!!

pgsql-advocacy by date

Next:From: Bruce MomjianDate: 2003-02-13 19:26:35
Subject: Re: set_ps_display on solaris x86
Previous:From: Bruce MomjianDate: 2003-02-13 18:49:06
Subject: Re: Changing the default configuration (was Re:

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group