Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 78C3064FD84 for ; Fri, 21 Nov 2008 16:48:24 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 77405-05 for ; Fri, 21 Nov 2008 16:48:20 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail.gransy.com (nathalia.gransy.com [82.208.29.194]) by mail.postgresql.org (Postfix) with ESMTP id 41BE8650439 for ; Fri, 21 Nov 2008 16:48:19 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by mail.gransy.com (Postfix) with ESMTP id C304F7AC1E2 for ; Fri, 21 Nov 2008 21:48:17 +0100 (CET) Received: from mail.gransy.com ([127.0.0.1]) by localhost (nathalia.gransy.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vfUk1Vv8A4KW for ; Fri, 21 Nov 2008 21:48:17 +0100 (CET) Received: from [192.168.1.1] (ip-89-102-139-23.karneval.cz [89.102.139.23]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.gransy.com (Postfix) with ESMTP id A109C7AC038 for ; Fri, 21 Nov 2008 21:48:17 +0100 (CET) Message-ID: <49271E95.5080200@fuzzy.cz> Date: Fri, 21 Nov 2008 21:48:21 +0100 From: Tomas Vondra User-Agent: Thunderbird 2.0.0.9 (X11/20080213) MIME-Version: 1.0 CC: pgsql-performance@postgresql.org Subject: Re: Hash join on int takes 8..114 seconds References: <49253FE1.3070706@archonet.com> <0205611B528C4C2CBA99AFC64E57D6E8@andrusnotebook> <75A918DFCF25470FAF96B3FE3D25A38B@andrusnotebook> <4926E2B2.9050202@archonet.com> <8A78204AA6D44C04B053E6412B244E13@andrusnotebook> <8D7F64CF7F614E13AC554D6CF86F39B2@andrusnotebook> <20081121191646.GH5210@alvh.no-ip.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.581 tagged_above=0 required=5 tests=MISSING_HEADERS=1.581 X-Spam-Level: * X-Archive-Number: 200811/196 X-Sequence-Number: 31927 > Thank you. > My 8.1.4 postgresql.conf does not contain such option. So > vacuum_cost_delay is off probably. > Since doc does not recommend any value, I planned to use 2000 > > Will value of 30 allow other clients to work when VACUUM FULL is running ? No, as someone already noted the VACUUM FULL is blocking anyway (and does not use this value at all). > Uncommented relevant values in postgresql.conf file are: > > shared_buffers = 15000 > work_mem = 512 I'd consider increasing this value a little - 0.5 MB seems too low to me (but not necessarily). > maintenance_work_mem = 131072 > fsync = on > effective_cache_size= 70000 Well, your server has 2GB of RAM and usually it's recommended to set this value to about 60-70% of your RAM, so using 540MB (25%) seems quite low. Anyway this is just a hint to PostgreSQL, it does not increase memory consumption or so - it's just an estimate of how much data are cached by kernel. Anyway, I don't expect these values have significant effect in case of the issue solved in this thread. regards Tomas