X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 9FD44B430AD for ; Sun, 6 Jul 2003 01:32:16 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 50715-03 for ; Sat, 5 Jul 2003 22:32:05 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.10.40.251]) by svr1.postgresql.org (Postfix) with ESMTP id 5B79EB427D9 for ; Sat, 5 Jul 2003 22:32:05 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3186415; Sat, 05 Jul 2003 18:32:24 -0700 Content-Type: text/plain; charset="iso-8859-1" From: Josh Berkus Organization: Aglio Database Solutions To: Sean Chittenden Subject: Re: Moving postgresql.conf tunables into 2003... Date: Sat, 5 Jul 2003 18:27:44 -0700 User-Agent: KMail/1.4.3 Cc: pgsql-performance@postgresql.org References: <20030703190502.GR72567@perrin.int.nxad.com> <200307051558.25484.josh@agliodbs.com> <20030706002413.GZ72567@perrin.int.nxad.com> In-Reply-To: <20030706002413.GZ72567@perrin.int.nxad.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200307051827.44848.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/106 X-Sequence-Number: 2399 Sean, > > That's exactly my point. We cannot provide enough documentation in > > the CONF file without septupling its length. IF we remove all > > commentary, and instead provide a pointer to the documentation, more > > DBAs will read it. > > Which I don't think would happen and why I think the terse bits that > are included are worth while. :) Depressingly enough, you are probably correct, unless we assemble a more user-friendly "getting started" guide. > *) concurrent disk activity > > A disk/database activity metric is different than the cost of a seek > on the platters. :) Because PostgreSQL doesn't currently support such > a disk concurrency metric doesn't mean that its definition should get > rolled into a different number in an attempt to accommodate for a lack > thereof. I was talking about concurrent activity by *other* applications. For example, if a DBA has a java app that is accessing XML on the same array as postgres 500 times/minute, then you'd need to adjust random_page_cost upwards to allow for the resource contest. > An "ideal" value isn't obtained via guess and check. Checking is only > the verification of some calculable set of settings....though right now > those calculated settings are guessed, unfortunately. > Works for me, though a benchmark will be less valuable than adding a > disk concurrency stat, improving data trend/distribution analysis, and > using numbers that are concrete and obtainable through the OS kernel > API or an admin manually plunking numbers in. I'm still recovering > from my move from Cali to WA so with any luck, I'll be settled in by > then. The idea is that for a lot of statistics, we're only going to be able to obtain valid numbers if you have something constant to check them against. Talk to you later this month! -- Josh Berkus Aglio Database Solutions San Francisco