From: Vivek Khera <khera@kcilink.com>
To: pgsql-performance@postgresql.org
Subject: Re: go for a script! / ex: PostgreSQL vs. MySQL
Date: Fri, 10 Oct 2003 16:22:08 -0400
Message-ID: <x71xtkq1vz.fsf@yertle.int.kciLink.com> (raw)
References: <B7397E6AC70AB1418180FA3480B9365556A69A@deun2kex01.realgarant.de>
<200310090956.11356.josh@agliodbs.com>
<20031009171715.GR2979@rlx11.zapatec.com>
<20031009181112.GA71907@perrin.nxad.com>
>>>>> "SC" == Sean Chittenden <sean@chittenden.org> writes:
SC> patches to extract info from their OS so that initdb can make useful
SC> decisions. Or, lastly, does anyone think that this should be in a
SC> different, external program? -sc
Well, there should definitely be a way to run a "get current best
tuning advice" for those times when I go and do something like add a
Gig of RAM. ;-)
Also, I'm sure the tuning advice will change over time, so having to
do initdb to get that advice would be a bit onerous.
As long as initdb has an option for just getting the tuning info, I
see no reason to make it separate.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: khera@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
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-performance@postgresql.org
Cc: khera@kcilink.com
Subject: Re: go for a script! / ex: PostgreSQL vs. MySQL
In-Reply-To: <x71xtkq1vz.fsf@yertle.int.kciLink.com>
* 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