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 E2FC6D1B215 for ; Fri, 18 Jun 2004 15:58:04 -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 44063-05 for ; Fri, 18 Jun 2004 18:58:00 +0000 (GMT) Received: from mpls-qmqp-01.inet.qwest.net (mpls-qmqp-01.inet.qwest.net [63.231.195.112]) by svr1.postgresql.org (Postfix) with SMTP id 23ABFD1B1A0 for ; Fri, 18 Jun 2004 15:57:58 -0300 (ADT) Received: (qmail 26657 invoked by uid 0); 18 Jun 2004 18:57:50 -0000 Received: from unknown (63.231.195.5) by mpls-qmqp-01.inet.qwest.net with QMQP; 18 Jun 2004 18:57:50 -0000 Received: from 63-227-127-37.dnvr.qwest.net (HELO ?10.0.0.2?) (63.227.127.37) by mpls-pop-05.inet.qwest.net with SMTP; 18 Jun 2004 18:57:45 -0000 Date: Fri, 18 Jun 2004 12:58:27 -0600 Message-Id: <1087585107.28062.16.camel@localhost.localdomain> From: "Scott Marlowe" To: "Joshua D. Drake" Cc: "Tom Lane" , "Domenico Sgarbossa" , pgsql-performance@postgresql.org Subject: Re: [BULK] Problems with vacuum! In-Reply-To: <40D338BC.7080705@commandprompt.com> 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> <1087582040.28062.13.camel@localhost.localdomain> <40D338BC.7080705@commandprompt.com> 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/202 X-Sequence-Number: 7260 I believe it was more like the kernel was tuned to make it less common, but certain things can still trigger it. I know the problem was still there in the 2.4.24 on the last server I was playing with, but it was a lot less of a problem than it had been under 2.4.9 on an earlier machine with the same basic amount of memory. On Fri, 2004-06-18 at 12:47, Joshua D. Drake wrote: > Hello, > > I would have to double check BUT I believe this is fixed in later 2.4.x > kernels as well. If you don't want to go through the hassle of 2.6 > (although it really is a nice kernel) then upgrade to 2.4.26. > > Sincerely, > > Joshau D. Drake > > Scott Marlowe wrote: > > 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. > > > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 4: Don't 'kill -9' the postmaster >