X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 4C4409DC9D8 for ; Tue, 31 Jan 2006 16:01:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 39348-08 for ; Tue, 31 Jan 2006 16:01:27 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id 0F6EF9DC89F for ; Tue, 31 Jan 2006 16:01:25 -0400 (AST) Received: from gghcwest.com (adsl-71-128-90-172.dsl.pltn13.pacbell.net [71.128.90.172]) by svr4.postgresql.org (Postfix) with ESMTP id 8F9CA5AF892 for ; Tue, 31 Jan 2006 20:01:26 +0000 (GMT) Received: from toonses.gghcwest.com (toonses.gghcwest.com [192.168.168.115]) by gghcwest.com (8.12.10/8.12.9) with ESMTP id k0VK1Lmd014413 for ; Tue, 31 Jan 2006 12:01:22 -0800 Received: from jwb by toonses.gghcwest.com with local (Exim 4.52) id 1F41go-0001U9-TW for pgsql-hackers@postgresql.org; Tue, 31 Jan 2006 12:01:22 -0800 Subject: Re: New project launched : PostgreSQL GUI Installer for From: "Jeffrey W. Baker" To: pgsql-hackers@postgresql.org In-Reply-To: <20060131190251.GQ95850@pervasive.com> References: <43DF4567.6080200@wildenhain.de> <43DF4DFB.2030008@pse-consulting.de> <20060131190251.GQ95850@pervasive.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Tue, 31 Jan 2006 12:01:22 -0800 Message-Id: <1138737682.5648.1.camel@toonses.gghcwest.com> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.06 required=5 tests=[AWL=0.060] X-Spam-Score: 0.06 X-Spam-Level: X-Archive-Number: 200601/1016 X-Sequence-Number: 79120 On Tue, 2006-01-31 at 13:02 -0600, Jim C. Nasby wrote: > On Tue, Jan 31, 2006 at 11:46:03AM +0000, Andreas Pflug wrote: > > Tino Wildenhain wrote: > > > > > > > >Figuring out the correct values for some of the buffers and costs > > >is still a bit tough. Otoh, I guess there is no easy way to predict > > >all these. > > > > pgAdmin has a mechanism to suggest values (currently for autovacuum and > > listen_address only), which waits for expansion :-) I could think of a > > wizard that asks decent questions, resulting in proposals. > > > > Whether implemented as GUI or not, a questionaire and suggested > > algorithms to calculate settings (eyeballed from Core) would be a good > > starting point. > > PostgreSQL *desperately* needs a better means of dealing with > configuration (though I guess I shouldn't be pushing too hard for this > since the current state of affairs brings me business). Any improvement > in this area would be very welcome. > http://pgfoundry.org/projects/configurator/ is something worth looking > at. An ideal facility would be a program that analyzes the workload at runtime and adjusts accordingly. That doesn't sound too hard, within some unambitious boundary. If anyone would like to work on this, I'd be happy to contribute. -jwb