From: Ron Mayer <rm_pg@cheapcomplexdevices.com>
To: Gregory Stark <stark@enterprisedb.com>
Cc: David E. Wheeler <david@kineticode.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Overhauling GUCS
Date: Sun, 01 Jun 2008 09:11:27 -0700
Message-ID: <4842CA2F.2040107@cheapcomplexdevices.com> (raw)
In-Reply-To: <87zlq6jo1o.fsf@oxford.xeocode.com>
References: <48409D1E.3070208@agliodbs.com>
<16866.1212251015@sss.pgh.pa.us>
<DFB26BD0-AD37-44F7-9255-BA78EC7E7FF8@kineticode.com>
<87zlq6jo1o.fsf@oxford.xeocode.com>
Gregory Stark wrote:
>
> I think we do a pretty good job of this already. Witness things like
> effective_cache_size -- imagine if this were "nested_loop_cache_hit_rate" for
> example, good luck figuring out what to set it to.
I think either of these are fine if we describe how to measure
them. Ideally if we had a GUC that said "log_nested_loop_cache_hit_rate"
that enabled some timing code (understandably with lots of overhead) that
made an attempt to measure the hit rate, it'd be easier to figure out
than the effective cache size, no?
> The vacuum cost delay factors are probably ripe for such a recast though. I
> think we need just one parameter "vacuum_io_bandwidth" or something like that.
+1; though perhaps the inverse of that is more useful. When my
machines are idle I'd be happy if they vacuum more. Wouldn't
we be better served specifying the I/O bandwidth of each device/tablespace
and letting vacuum use whatever portion would be otherwise idle?
> The bgwriter parameters might also be a candidate but I'm less certain.
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: rm_pg@cheapcomplexdevices.com, stark@enterprisedb.com, david@kineticode.com, tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Overhauling GUCS
In-Reply-To: <4842CA2F.2040107@cheapcomplexdevices.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