pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Martijn van Oosterhout <kleptog@svana.org>
To: Rainer Bauer <usenet@munnin.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Thu, 5 Jun 2008 17:18:02 +0200
Message-ID: <20080605151802.GC16690@svana.org> (raw)
In-Reply-To: <u38e44hd43noiihgcdarflv9f5320i2kdi@4ax.com>
References: <48409D1E.3070208@agliodbs.com>
	<484418D9.5040608@sun.com>
	<Pine.GSO.4.64.0806021227100.4018@westnet.com>
	<200806021106.05833.josh@agliodbs.com>
	<0B854D92-C5C2-4138-A0FE-F81892A33869@sun.com>
	<Pine.GSO.4.64.0806032324550.10282@westnet.com>
	<72DA5875-8E89-4A6F-8D0B-7F9A869D79B9@kineticode.com>
	<162867790806041331rce6eb94pb5d31b26892329ea@mail.gmail.com>
	<u38e44hd43noiihgcdarflv9f5320i2kdi@4ax.com>

On Thu, Jun 05, 2008 at 01:23:53AM +0200, Rainer Bauer wrote:
> I think it would be an enourmous help for beginners if they had a "simple"
> tuning tool which would tell them which values where altered (and possibly
> why) from Postgres' default settings based on some basic information.
> Like:
> - machine hardware (disk layout, OS, installed memory, etc.)
> - application usage (no. of clients, read/write activity, etc)

It would be possible to make a program that worked like:
# pg_autotune
Detected 4GB memory, 2.3GB free
Measured random_page_cost=2.3
Select expected usage: (d)edicated, (n)ormal, (t)iny
> t
Shared_buffers 64MB
Configuration stored to /etc/postgresql/8.3/postgresql.conf
#

This would probably solve most issues.

Have a nice day,
-- 
Martijn van Oosterhout   <kleptog@svana.org>   http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while 
> boarding. Thank you for flying nlogn airlines.

Attachments:

  signature.asc (application/pgp-signature, 188B) download

view thread (226+ messages)  latest in thread

Message-ID: <20080605151802.GC16690@svana.org>
Permalink:  ../20080605151802.GC16690@svana.org/
Also on:    postgresql.org/message-id/20080605151802.GC16690@svana.org

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: kleptog@svana.org, usenet@munnin.com
  Subject: Re: Overhauling GUCS
  In-Reply-To: <20080605151802.GC16690@svana.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox