X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id 81FDBD1C9EE for ; Wed, 6 Aug 2003 18:13:37 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 64849-01 for ; Wed, 6 Aug 2003 15:12:15 -0300 (ADT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 9BB64D1CA00 for ; Wed, 6 Aug 2003 15:13:26 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h76IDJSa001567; Wed, 6 Aug 2003 14:13:20 -0400 (EDT) To: Yaroslav Mazurak Cc: pgsql-performance@postgresql.org Subject: Re: PostgreSQL performance problem -> tuning In-reply-to: <3F30AF9E.2080607@lviv.bank.gov.ua> References: <3F30AF9E.2080607@lviv.bank.gov.ua> Comments: In-reply-to Yaroslav Mazurak message dated "Wed, 06 Aug 2003 10:34:54 +0300" Date: Wed, 06 Aug 2003 14:13:19 -0400 Message-ID: <1566.1060193599@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/105 X-Sequence-Number: 2922 Yaroslav Mazurak writes: > Current postgresql.conf settings (some) are: > max_locks_per_transaction = 16 This strikes me as a really bad idea --- you save little space by reducing it from the default, and open yourself up to unexpected failures. > wal_buffers = 256 That is almost certainly way more than you need. > sort_mem = 131072 People have already told you that one's a bad idea. > commit_delay = 32000 I'm unconvinced that setting this nonzero is a good idea. Have you done experiments to prove that you get a benefit? > enable_seqscan = false This is the cause of the bizarre-looking cost estimates. I don't recommend setting it false as a system-wide setting. If you want to nudge the planner towards indexscans, reducing random_page_cost a little is probably a better way. regards, tom lane