From: Joshua D. Drake <jd@commandprompt.com>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: Decibel! <decibel@decibel.org>
Cc: Josh Berkus <josh@agliodbs.com>
Subject: Re: Overhauling GUCS
Date: Fri, 06 Jun 2008 08:55:21 -0700
Message-ID: <48495DE9.9040409@commandprompt.com> (raw)
In-Reply-To: <200806061750.55582.peter_e@gmx.net>
References: <48409D1E.3070208@agliodbs.com>
<200806061435.01196.peter_e@gmx.net>
<1669.1212765410@sss.pgh.pa.us>
<200806061750.55582.peter_e@gmx.net>
Peter Eisentraut wrote:
> Am Freitag, 6. Juni 2008 schrieb Tom Lane:
>> Peter Eisentraut <peter_e@gmx.net> writes:
>>> - If we know better values, why don't we set them by default?
>> The problem is: better for what? In particular, I'm uncomfortable with
>> any changes in the direction of trying to make Postgres take over the
>> entire machine by default. I'd want some fairly explicit permission
>> from the user for that ...
>
> Yes, those are decisions we are going to have to make, eventually. But recall
> the three step process:
>
> 1. What values need changing?
shared_buffers
work_mem
maintenance_work_mem
checkpoint_segments
wal_sync_method
effective_cache_size
> I haven't seen a proposal for item 1 yet, so the rest is idle discussion at
> this time.
I think those cover the biggest low hanging fruit, async_commit is arguable.
Sincerely,
Joshua D. Drake
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: jd@commandprompt.com, peter_e@gmx.net, tgl@sss.pgh.pa.us, gsmith@gregsmith.com, pgadmin@pse-consulting.de, decibel@decibel.org, josh@agliodbs.com
Subject: Re: Overhauling GUCS
In-Reply-To: <48495DE9.9040409@commandprompt.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