From: ipig <ipig@ercist.iscas.ac.cn>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Google SoC--Idea Request
Date: Tue, 25 Apr 2006 14:33:22 +0800
Message-ID: <007001c66832$30efc030$8c01a8c0@homepig> (raw)
References: <20060417205455.GP49405@pervasive.com>
<36e682920604190909p68649a35m1953a7b4262b8852@mail.gmail.com>
<20060423214524.GC4775@surnet.cl>
<36e682920604231522w96183d0mbedfd7c70d574b58@mail.gmail.com>
<20060424165112.GD38186@pervasive.com>
<8743.1145932591@sss.pgh.pa.us>
<36e682920604241956s2bdd8880q2c479740d893c6fd@mail.gmail.com>
<9008.1145934318@sss.pgh.pa.us>
<20060425050017.GC81249@pervasive.com>
<444DB6F3.6000504@dunslane.net>
<36e682920604242250r13108475x91e4bb55045e0d16@mail.gmail.com>
<10889.1145945815@sss.pgh.pa.us>
Maybe you can develop a graphic interface just like Fedora Core setup interface which can choose packages installing, then the user can choose config file and then have a little change in parameters.
----- Original Message -----
From: "Tom Lane" <tgl@sss.pgh.pa.us>
To: "Jonah H. Harris" <jonah.harris@gmail.com>
Cc: "Andrew Dunstan" <andrew@dunslane.net>; "Jim C. Nasby" <jnasby@pervasive.com>; "John DeSoi" <desoi@pgedit.com>; "Pgsql Hackers" <pgsql-hackers@postgresql.org>
Sent: Tuesday, April 25, 2006 2:16 PM
Subject: Re: [HACKERS] Google SoC--Idea Request
> "Jonah H. Harris" <jonah.harris@gmail.com> writes:
>> On 4/25/06, Andrew Dunstan <andrew@dunslane.net> wrote:
>>> Personally I would much rather see a tuning advisor tool in more general
>>> use than just provide small/medium/large config setting files.
>
>> True dat.
>
> One thing that has to be figured out before we can go far with this
> is the whole question of how much smarts initdb really ought to have.
> Since a lot of packagers think that initdb should be run
> non-interactively behind the scenes, the obvious solution of "give
> initdb a --small/--medium/--large parameter" does not work all that
> nicely. But on the other hand we can't just tell people to drop in
> replacement config files when the one in place contains initdb-created
> specifics, such as locale settings.
>
> Now that there's a provision for "include" directives in
> postgresql.conf, one way to address this would be to split the
> config info into multiple physical files, some containing purely
> performance-related settings while others consider functionality.
> But that seems more like a wart than a solution to me. I feel that
> we've pushed performance-tuning logic into initdb that probably ought
> not be there, and we ought to factor it out again.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org
>
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: ipig@ercist.iscas.ac.cn, tgl@sss.pgh.pa.us
Subject: Re: Google SoC--Idea Request
In-Reply-To: <007001c66832$30efc030$8c01a8c0@homepig>
* 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