Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id E046A2E0289 for ; Thu, 5 Jun 2008 12:37:35 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 97914-01-4 for ; Thu, 5 Jun 2008 12:37:27 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from svana.org (svana.org [203.190.233.187]) by developer.postgresql.org (Postfix) with ESMTP id 0D3A22E02BD for ; Thu, 5 Jun 2008 12:18:11 -0300 (ADT) Received: from kleptog by svana.org with local (Exim 4.63) (envelope-from ) id 1K4HE2-0004zr-Ad; Fri, 06 Jun 2008 01:18:02 +1000 Date: Thu, 5 Jun 2008 17:18:02 +0200 From: Martijn van Oosterhout To: Rainer Bauer Cc: pgsql-hackers@postgresql.org Subject: Re: Overhauling GUCS Message-ID: <20080605151802.GC16690@svana.org> Reply-To: Martijn van Oosterhout References: <48409D1E.3070208@agliodbs.com> <484418D9.5040608@sun.com> <200806021106.05833.josh@agliodbs.com> <0B854D92-C5C2-4138-A0FE-F81892A33869@sun.com> <72DA5875-8E89-4A6F-8D0B-7F9A869D79B9@kineticode.com> <162867790806041331rce6eb94pb5d31b26892329ea@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZmUaFz6apKcXQszQ" Content-Disposition: inline In-Reply-To: X-PGP-Key-ID: Length=1024; ID=0x6F0B424C X-PGP-Key-Fingerprint: 34A8 8EAC F902 8C8D CA72 DCC7 201E DB34 6F0B 424C User-Agent: Mutt/1.5.13 (2006-08-11) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: kleptog@svana.org X-SA-Exim-Scanned: No (on svana.org); SAEximRunCond expanded to false X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200806/233 X-Sequence-Number: 119346 --ZmUaFz6apKcXQszQ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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=3D2.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, --=20 Martijn van Oosterhout http://svana.org/kleptog/ > Please line up in a tree and maintain the heap invariant while=20 > boarding. Thank you for flying nlogn airlines. --ZmUaFz6apKcXQszQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFISAOqIB7bNG8LQkwRAtqyAJ94WYbR4rgu1xeg10qlsGgXbP10jgCeKY0E 5Zh60CmDqJru/lG86wuaULc= =tvOi -----END PGP SIGNATURE----- --ZmUaFz6apKcXQszQ--