From: | Greg Smith <gsmith(at)gregsmith(dot)com> |
---|---|
To: | Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com> |
Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Simple postgresql.conf wizard |
Date: | 2008-12-04 00:47:32 |
Message-ID: | Pine.GSO.4.64.0812031942260.781@westnet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 3 Dec 2008, Guillaume Smet wrote:
> - it would be really nice to make it work with Python 2.4 as RHEL 5 is
> a Python 2.4 thing and it is a very widespread platform out there,
The 2.5 stuff is only required in order to detect memory on Windows. My
primary box is RHEL5 and runs 2.4, it works fine there.
> - considering the audience of this tool, I think you should explain in
> the usage text which type of workload implies each database type (DW,
> OLTP, Web, Mixed, Desktop).
Once I'm done with the docs I'll refer over to those, it's too much to put
into the usage without cluttering it.
> - it would be nice to be able to define the architecture (32-64 bits)
> from the command line (especially considering I won't be able to run
> it on our target boxes which are all RHEL 5 :))
I'm starting to lean toward making everything that gets detected as also
being possible to override, for these case. I want to make this just work
in as many cases as possible, but the situation where someone is
configuring/testing on a system other than the server is pretty common.
Now that I think about it I often setup configs on my 32-bit laptop and
them move them over onto 64-bit servers.
--
* Greg Smith gsmith(at)gregsmith(dot)com http://www.gregsmith.com Baltimore, MD
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-12-04 00:55:22 | Re: Simple postgresql.conf wizard |
Previous Message | Greg Smith | 2008-12-04 00:34:50 | Re: Simple postgresql.conf wizard |