From: | Steve Atkins <steve(at)blighty(dot)com> |
---|---|
To: | PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>, PostgreSQL-documentation <pgsql-docs(at)postgresql(dot)org> |
Subject: | Re: Volunteer to build a configuration tool |
Date: | 2007-06-18 23:35:11 |
Message-ID: | B0391D67-65F6-4D52-BF65-AFFB144EC1D3@blighty.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-performance |
On Jun 18, 2007, at 4:09 PM, david(at)lang(dot)hm wrote:
> one thing to point out to people about this idea is that nothing
> says that this page needs to be served via a webserver. If all the
> calculations are done in javascript this could be a local file that
> you open with a browser.
>
> do any of the text-mode browsers implement javascript? if so then
> you have an answer even for the deeply buried isolated headless
> servers.
It doesn't really matter.
The implementation is likely to be trivial, and could be independently
knocked out by anyone in their favorite language in a few hours.
The tricky bits are going to be defining the problem and creating the
alogrithm to do the maths from input to output.
If that's so, the language or platform the proof-of-concept code is
written for isn't that important, as it's likely to be portable to
anything
else without too much effort.
But the tricky bits seem quite tricky (and the first part, defining the
problem, is something where someone developing it on their
own, without some discussion with other users and devs
could easily end up way off in the weeds).
Cheers,
Steve
>
> David Lang
>
> On Mon, 18 Jun 2007, Campbell, Lance wrote:
>
>> I am a Java Software architect, DBA, and project manager for the
>> University of Illinois, Department of Web Services. We use
>> PostgreSQL
>> to serve about 2 million pages of dynamic content a month; everything
>> from calendars, surveys, forms, discussion boards, RSS feeds,
>> etc. I am
>> really impressed with this tool.
>>
>>
>>
>> The only major problem area I have found where PostgreSQL is really
>> lacking is in "what should my initial configuration settings be?" I
>> realize that there are many elements that can impact a DBA's specific
>> database settings but it would be nice to have a "configuration tool"
>> that would get someone up and running better in the beginning.
>>
>>
>>
>> This is my idea:
>>
>>
>>
>> A JavaScript HTML page that would have some basic questions at the
>> top:
>>
>> 1) How much memory do you have?
>>
>> 2) How many connections will be made to the database?
>>
>> 3) What operating system do you use?
>>
>> 4) Etc...
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: explain analyze is your friend
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2007-06-19 00:05:23 | Re: Volunteer to build a configuration tool |
Previous Message | david | 2007-06-18 23:09:34 | Re: Volunteer to build a configuration tool |
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2007-06-19 00:05:23 | Re: Volunteer to build a configuration tool |
Previous Message | david | 2007-06-18 23:09:34 | Re: Volunteer to build a configuration tool |