From: Justin Clift <justin@postgresql.org>
To: Josh Berkus <josh@agliodbs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Merlin Moncure <merlin.moncure@rcsonline.com>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>
Cc: pgsql-advocacy@postgresql.org
Subject: Re: Changing the default configuration (was Re:
Date: Wed, 12 Feb 2003 04:29:19 +1100
Message-ID: <3E4932EF.3070604@postgresql.org> (raw)
In-Reply-To: <200302110918.48614.josh@agliodbs.com>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local>
<26004.1044980414@sss.pgh.pa.us>
<3E492E06.2030702@postgresql.org>
<200302110918.48614.josh@agliodbs.com>
Josh Berkus wrote:
> Tom, Justin,
<snip>
>
> What if we supplied several sample .conf files, and let the user choose which
> to copy into the database directory? We could have a "high read
> performance" profile, and a "transaction database" profile, and a
> "workstation" profile, and a "low impact" profile. We could even supply a
> Perl script that would adjust SHMMAX and SHMMALL on platforms where this can
> be done from the command line.
This might have value as the next step in the process of:
a) Are we going to have better defaults?
or
b) Let's stick with the current approach.
If we decide to go with better (changed) defaults, we may also be able
to figure out a way of having profiles that could optionally be chosen from.
As a longer term thought, it would be nice if the profiles weren't just
hard-coded example files, but more of:
pg_autotune --setprofile=xxx
Or similar utility, and it did all the work. Named profiles being one
capability, and other tuning measurements (i.e. cpu costings, disk
performance profiles, etc) being the others.
Regards and best wishes,
Justin Clift
--
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
- Indira Gandhi
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: justin@postgresql.org, josh@agliodbs.com, tgl@sss.pgh.pa.us, merlin.moncure@rcsonline.com, pgsql-hackers@postgresql.org, pgsql-advocacy@postgresql.org
Subject: Re: Changing the default configuration (was Re:
In-Reply-To: <3E4932EF.3070604@postgresql.org>
References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <26004.1044980414@sss.pgh.pa.us> <3E492E06.2030702@postgresql.org> <200302110918.48614.josh@agliodbs.com> <3E4932EF.3070604@postgresql.org>
* 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