Re: New project launched : PostgreSQL GUI Installer for - Mailing list pgsql-hackers

From Jeffrey W. Baker
Subject Re: New project launched : PostgreSQL GUI Installer for
Date
Msg-id 1138737682.5648.1.camel@toonses.gghcwest.com
Whole thread Raw
In response to Re: New project launched : PostgreSQL GUI Installer for  ("Jim C. Nasby" <jnasby@pervasive.com>)
Responses Re: Configuration WAS: New project launched : PostgreSQL GUI Installer for  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Joachim Wieland
Date:
Subject: Re: Policy on schema-qualified names
Next
From: "Michael Paesold"
Date:
Subject: Re: Tab completion of SET TRANSACTION ISOLATION