Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 138F41337BA3 for ; Fri, 7 Jan 2011 14:46:25 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 11624-07 for ; Fri, 7 Jan 2011 18:46:17 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by mail.postgresql.org (Postfix) with ESMTP id 455B51337B92 for ; Fri, 7 Jan 2011 14:46:17 -0400 (AST) Received: from [192.168.1.7] (mail.highperformancepostgresql.com [71.179.240.8]) by mrelayeu.kundenserver.de (node=mreu2) with ESMTP (Nemesis) id 0Lnnzv-1QFFuM43FH-00hZ2C; Fri, 07 Jan 2011 19:46:15 +0100 Message-ID: <4D275F74.3040405@2ndquadrant.com> Date: Fri, 07 Jan 2011 13:46:12 -0500 From: Greg Smith User-Agent: Thunderbird 2.0.0.24 (X11/20100317) MIME-Version: 1.0 To: Samuel Gendler CC: Tom Lane , Josh Berkus , Jeff Janes , pgsql-performance@postgresql.org Subject: Re: Wrong docs on wal_buffers? References: <4D24D7DE.6020507@agliodbs.com> <4D2610F3.8070407@agliodbs.com> <4D269899.6040901@2ndquadrant.com> <18962.1294412821@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:UrpUQxOxJGNZEpI1Hf20QWk8XQ30cNAurpw4emay39C OqxXhIoSnA/dCUrdYvf4E3oMfWQd6aQoVk/8deTJ9ROqjfYjvf 4YbwRGPcs2JNwrWWhAK39Dni7/9I9D8IRXzkWXVctTenJGKyJp 4slBWytds7mm5KuZBpAPoH9Yk3jNq8oowvMxdL/pkiFp0Ew0cY r/l5EUSWYFh7YhrQYdxhfCSLMA8i5hWLHvs+gQscZg= X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.9 tagged_above=-10 required=5 tests=BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001 X-Spam-Level: X-Archive-Number: 201101/49 X-Sequence-Number: 41836 Samuel Gendler wrote: > I was trying to make the point that, in an attempt to make things very > easy for novice users, we are actually making them quite a bit more > complex for novice users who want to do anything besides start the server. People who can't start the server often abandon PostgreSQL, never come back again. And in the worst case, they popularize their frustration via blogs etc. That contributes to the perception the program is hard to use far more than people who run into problems only with performance--people expect database tuning to be non-trivial, but they have minimal tolerance for trouble when first trying to use a program. From an advocacy perspective, there is no higher priority than making sure things work as smoothly as feasible for people who have never run PostgreSQL before. Changing the software so it doesn't work out of the box on a system with minimal shared memory defaults, as seen on Linux and other operating systems, would be one of the worst possible changes to the database anyone could make. About once a month now I came across someone who used my pgtune program: https://github.com/gregs1104/pgtune to get a reasonable starting configuration. That program is still rough and has limitations, but the general idea turns out to work just fine. I'm bored with discussions about making this easier for users unless they involve people volunteering to help with the coding needed to turn that, or something better than it, into a release quality tool. The path to sort this out is mapped out in excruciating detail from my perspective. The only thing missing are code contributors with time to walk down it. So far it's me, occasional code refinement from Matt Harrison, some packager help, and periodic review from people like Josh Berkus. And that's just not good enough to make progress on this particular front quickly enough. -- Greg Smith 2ndQuadrant US greg@2ndQuadrant.com Baltimore, MD PostgreSQL Training, Services and Support www.2ndQuadrant.us "PostgreSQL 9.0 High Performance": http://www.2ndQuadrant.com/books