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 1A5EBD1B37D for ; Fri, 18 Jun 2004 15:06:38 -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 12581-07 for ; Fri, 18 Jun 2004 18:06:36 +0000 (GMT) Received: from mpls-qmqp-03.inet.qwest.net (mpls-qmqp-03.inet.qwest.net [63.231.195.114]) by svr1.postgresql.org (Postfix) with SMTP id 7C44FD1B345 for ; Fri, 18 Jun 2004 15:06:33 -0300 (ADT) Received: (qmail 16678 invoked by uid 0); 18 Jun 2004 17:37:57 -0000 Received: from mpls-pop-03.inet.qwest.net (63.231.195.3) by mpls-qmqp-03.inet.qwest.net with QMQP; 18 Jun 2004 17:37:57 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-03.inet.qwest.net with SMTP; 18 Jun 2004 18:06:33 -0000 Date: Fri, 18 Jun 2004 12:07:20 -0600 Message-Id: <1087582040.28062.13.camel@localhost.localdomain> From: "Scott Marlowe" To: "Tom Lane" Cc: "Domenico Sgarbossa" , pgsql-performance@postgresql.org Subject: Re: [BULK] Problems with vacuum! In-Reply-To: <20554.1087571463@sss.pgh.pa.us> References: <003c01c44fbd$c84a6af0$2500fa0a@CardServices.TCI.com> <004c01c44fc3$d7cdeaf0$70c8007e@xtecnica.it> <87pt8616i3.fsf@asmodeus.mcnaught.org> <1087226647.1775.14.camel@kaos> <011101c4553b$c1967130$70c8007e@xtecnica.it> <20554.1087571463@sss.pgh.pa.us> Content-Type: text/plain Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/200 X-Sequence-Number: 7258 On Fri, 2004-06-18 at 09:11, Tom Lane wrote: > "Domenico Sgarbossa" writes: > > 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, > > A sane kernel should drop disk buffers rather than swapping. We heard > recently about a bug in some versions of the Linux kernel that cause it > to prefer swapping to discarding disk cache, though. It sounds like > that's what you're hitting. Look into newer kernels ... This was a common problem in the linux 2.4 series kernels, but has supposedly been fixed in the 2.6 kernels. Having lots of memory and turning off swap will "fix" the problem in 2.4, but if you run out of real mem, you're hosed.