X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id C72CFD1B4E5 for ; Fri, 18 Jun 2004 10:55:47 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 30042-09 for ; Fri, 18 Jun 2004 13:55:43 +0000 (GMT) Received: from xtecnica.com (host154-218.pool80206.interbusiness.it [80.206.218.154]) by svr1.postgresql.org (Postfix) with ESMTP id 79088D1B267 for ; Fri, 18 Jun 2004 10:55:37 -0300 (ADT) Received: from DOMENICO2K by xtecnica.com (MDaemon.PRO.v7.1.0.R) with ESMTP id md50000022350.msg for ; Fri, 18 Jun 2004 15:54:48 +0200 Message-ID: <011101c4553b$c1967130$70c8007e@xtecnica.it> Reply-To: "Domenico Sgarbossa" From: "Domenico Sgarbossa" To: References: <003c01c44fbd$c84a6af0$2500fa0a@CardServices.TCI.com><004c01c44fc3$d7cdeaf0$70c8007e@xtecnica.it> <87pt8616i3.fsf@asmodeus.mcnaught.org> <1087226647.1775.14.camel@kaos> Subject: Re: [BULK] Problems with vacuum! Date: Fri, 18 Jun 2004 15:54:20 +0200 Organization: XTECNICA srl MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 1 X-MSMail-Priority: High X-Mailer: Microsoft Outlook Express 5.50.4927.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200 X-Authenticated-Sender: domenico@xtecnica.com X-Spam-Processed: xtecnica.com, Fri, 18 Jun 2004 15:54:48 +0200 (not processed: message from valid local sender) X-MDRemoteIP: 126.0.200.112 X-Return-Path: domenico@xtecnica.com X-MDaemon-Deliver-To: pgsql-performance@postgresql.org X-MDAV-Processed: xtecnica.com, Fri, 18 Jun 2004 15:54:52 +0200 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.0 tagged_above=0.0 required=5.0 tests=X_MSMAIL_PRIORITY_HIGH, X_PRIORITY_HIGH X-Spam-Level: * X-Archive-Number: 200406/188 X-Sequence-Number: 7246 The problems still remains... I've tried to change shmax to 128 mb (i've got 2 GB of ram), then the others parameter are set as follow: shared_buffers = 8096 # 2*max_connections, min 16 max_fsm_relations = 500 # min 10, fsm is free space map max_fsm_pages = 15000 # min 1000, fsm is free space map max_locks_per_transaction = 64 # min 10 wal_buffers = 8 # min 4 # # Non-shared Memory Sizes # sort_mem = 1024 # min 32 vacuum_mem = 16384 # min 1024 I've scheduled 2 tasks nightly: vacuumdb --analyze dbname pg_dump -x -f dbname.dmp dbname so when the users go home, i've got something like 15/20000kb free ram, the rest is cached and 0kb of swap... It seems that when pg_dump starts the cached memory isn't released so the system begin to swap, then the system does the same with vacuum..... even if there 1.8 gb of cached ram (that is'nt released anymore....) very strange! anyone could explain mw why this happend? Distinti Saluti Sgarbossa Domenico X Tecnica S.R.L. www.xtecnica.com Tel: 049/9409154 - 049/5970297 Fax: 049/9400288