X-Original-To: pgsql-advocacy@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 5828F475CB4; Tue, 11 Feb 2003 12:18:06 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id A9D87475C9E; Tue, 11 Feb 2003 12:18:05 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1BHIA5u026501; Tue, 11 Feb 2003 12:18:10 -0500 (EST) To: Justin Clift Cc: Merlin Moncure , PostgresSQL Hackers Mailing List , pgsql-advocacy@postgresql.org Subject: Re: Changing the default configuration (was Re: [HACKERS] PostgreSQL Benchmarks) In-reply-to: <3E492E06.2030702@postgresql.org> References: <303E00EBDD07B943924382E153890E5434A909@cuthbert.rcsinc.local> <26004.1044980414@sss.pgh.pa.us> <3E492E06.2030702@postgresql.org> Comments: In-reply-to Justin Clift message dated "Wed, 12 Feb 2003 04:08:22 +1100" Date: Tue, 11 Feb 2003 12:18:10 -0500 Message-ID: <26500.1044983890@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/15 X-Sequence-Number: 773 Justin Clift writes: > Personally I'd be a bunch happier if we set the buffers so high that we > definitely have decent performance, and the people that want to run > PostgreSQL are forced to make the choice of either: > 1) Adjust their system settings to allow PostgreSQL to run properly, or > 2) Manually adjust the PostgreSQL settings to run memory-constrained > This way, PostgreSQL either runs decently, or they are _aware_ that > they're limiting it. Yeah, that is the subtext here. If you can't increase SHMMAX then you can always trim the postgresql.conf parameters --- but theoretically, at least, you should then have a clue that you're running a badly-configured setup ... regards, tom lane