pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nick Fankhauser <nickf@ontko.com>
To: josh@agliodbs.com
To: pgsql-performance@postgresql.org
Cc: pgsql-advocacy@postgresql.org
Subject: A bit OT- RE: [PERFORM] Re-ordering .CONF params ... questions for this list
Date: Sat, 14 Jun 2003 09:40:30 -0500
Message-ID: <NEBBLAAHGLEEPCGOBHDGCEIHHJAA.nickf@ontko.com> (raw)
In-Reply-To: <200306131551.14891.josh@agliodbs.com>

> 2) I just spent 4.5 hours re-arranging the Runtime-config docs page last
> night, and am very reluctant to do it again.

I like this reason... I think you've already done a great service by
creating functional groups. The newbies won't be hurt by the need to scroll
down a bit, and the functional groupings already serve to eliminate the
confusion about what the params are for (which *does* hurt them). What
you've done is a great improvement. My additional comments below are offered
in the spirit of support for what you've already done along with thoughts to
consider for future revisions.





> 1) I mess around with postgresql.conf constantly, and seldom
> touch anything in
> the "client connection defaults" section.  I do, however, mess
> with the stuff
> in the "resource usage" section, as to most of the people on this list.

I agree... but are we the folks that the conf file needs to be made more
intuitive for?

If the intent is to make it easier for experienced folks like ourselves who
are working with large or unusual databases to deal with PostgreSQL, then
certainly the resource usage and tuning settings should go to the top. We'll
set the other params once & never touch them again.

On the other hand, I suspect that the majority of postgresql users play with
the other params a bit during install to get their systems working and never
touch the resource usage or tuning params ever. (And this is as it should
be, given that the defaults are reasonable for most systems.)

Part of my motivation in offering this advice is our sibling rivalry with
MySQL- once we look under the hood, we usually find that PostgreSQL is the
way to go, but all of us mechanics spend a silly amount of time wondering
aloud why the many people who don't enjoy looking under the hood don't get
it. If we want the legions of MySQL followers to get it, we need to put only
the necessary instruments on the dashboard and not force non-mechanics to
look under the hood. (And to stretch the metaphor a bit further- The hood
latch still needs to be near the dashboard for the folks who are ready for
the next step.)


I'll cross-post this to advocacy because I'm tottering off on that tangent.
I think the comments may be useful in this forum as well because the
advocacy folks need to pass thoughts to the active developers & documenters
in much the same way that marketing folks need to communicate well with
engineers in the commercial world.


Regards,
      -Nick




view thread (2+ messages)  latest in thread

Message-ID: <NEBBLAAHGLEEPCGOBHDGCEIHHJAA.nickf@ontko.com>
Permalink:  ../NEBBLAAHGLEEPCGOBHDGCEIHHJAA.nickf@ontko.com/
Also on:    postgresql.org/message-id/NEBBLAAHGLEEPCGOBHDGCEIHHJAA.nickf@ontko.com

 · 

reply

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: nickf@ontko.com, josh@agliodbs.com, pgsql-advocacy@postgresql.org
  Subject: Re: A bit OT- RE: [PERFORM] Re-ordering .CONF params ... questions for this list
  In-Reply-To: <NEBBLAAHGLEEPCGOBHDGCEIHHJAA.nickf@ontko.com>
  References: <200306131551.14891.josh@agliodbs.com> <NEBBLAAHGLEEPCGOBHDGCEIHHJAA.nickf@ontko.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