Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id BAC286502D0; Tue, 12 Aug 2008 16:43:58 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 89283-08; Tue, 12 Aug 2008 16:43:49 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from westnet.com (westnet.com [216.187.52.2]) by postgresql.org (Postfix) with ESMTP id D24D5650278; Tue, 12 Aug 2008 16:43:51 -0300 (ADT) Received: from westnet.com (localhost [127.0.0.1]) by westnet.com (8.14.0/8.14.0) with ESMTP id m7CJhjjC005966; Tue, 12 Aug 2008 15:43:45 -0400 (EDT) Received: from localhost (gsmith@localhost) by westnet.com (8.14.0/8.13.2/Submit) with ESMTP id m7CJhiie005958; Tue, 12 Aug 2008 15:43:44 -0400 (EDT) X-Authentication-Warning: westnet.com: gsmith owned process doing -bs Date: Tue, 12 Aug 2008 15:43:44 -0400 (EDT) From: Greg Smith X-X-Sender: gsmith@westnet.com To: Bruce Momjian cc: Greg Sabino Mullane , pgsql-docs@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: [HACKERS] [ADMIN] shared_buffers and shmmax In-Reply-To: <200808121748.m7CHmfX26268@momjian.us> Message-ID: References: <200808121748.m7CHmfX26268@momjian.us> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200808/3 X-Sequence-Number: 4943 On Tue, 12 Aug 2008, Bruce Momjian wrote: >> There's already some changes needed in this area needed to execute the >> full GUC cleanup/wizard plan that's being worked on. The pg_settings view >> really should show the value both as the user input it and as it's stored >> internally for cases like these, which lowers the confusion here a bit >> even without going so far as converting everything to bytes. > > Is this a TODO? I don't think you need yet another TODO for every detail, the existing TODO "Add external tool to auto-tune some postgresql.conf parameters" has to squash a bunch of issues in this area. This particular issue Greg raised will already be improved significantly if executing the larger project plan at http://wiki.postgresql.org/wiki/GUCS_Overhaul This week Robert Treat and I have been doing a lot of work on "Problem #1" there, "Most people have no idea how to set [GUCs]" which I know some people wanted to see a more formal document for before mucking with any of the code. I'll have something to announce there shortly. -- * Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD