| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Greg Smith" <gsmith(at)gregsmith(dot)com> |
| Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, "Ron Mayer" <rm_pg(at)cheapcomplexdevices(dot)com>, <jd(at)commandprompt(dot)com>, "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Simple postgresql.conf wizard |
| Date: | 2008-12-04 22:15:01 |
| Message-ID: | 49380205.EE98.0025.0@wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> Greg Smith <gsmith(at)gregsmith(dot)com> wrote:
> On Thu, 4 Dec 2008, Kevin Grittner wrote:
>
>> I think there needs to be some easy way to choose an option which
>> yields a configuration similar to what we've had in recent
production
>> releases -- something that will start up and allow minimal testing
on
>> even a small machine.
>
> But that's the goal of what comes out of initdb already; I'm missing
how
> that is something this script would even get involved in. Is your
> suggestion to add support for a minimal target that takes a tuned-up
> configuration file and returns it to that state, or did you have
something
> else in mind?
Perhaps I misunderstood some earlier post -- I had gotten the
impression that initdb was going to use this utility for the initial
postgresql.conf file. If that's not happening, then you can ignore my
last post as noise, with my apologies.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2008-12-04 22:27:12 | Re: In-place upgrade: catalog side |
| Previous Message | Gregory Stark | 2008-12-04 22:11:51 | Re: contrib/pg_stat_statements 1202 |