X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id E607AD1F23C for ; Wed, 5 May 2004 22:16:41 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 28648-07 for ; Wed, 5 May 2004 22:16:25 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 4B8FBD1F240 for ; Wed, 5 May 2004 22:16:21 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i461GKSx044346 for ; Thu, 6 May 2004 01:16:20 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i4619UvG040033 for pgsql-admin@postgresql.org; Thu, 6 May 2004 01:09:30 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.admin Subject: Re: Postmaster hogs CPU Date: Thu, 06 May 2004 03:09:25 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 15 Message-ID: <40999045.2030502@bigfoot.com> References: <1083773198.21180.464.camel@camel> <20040505200355.43021.qmail@web13807.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Chris Gamache User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en In-Reply-To: <20040505200355.43021.qmail@web13807.mail.yahoo.com> To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/52 X-Sequence-Number: 13368 Chris Gamache wrote: > What can be done to allow for smarter preemption? Could I do anything at the OS > level to throttle that particular postmaster's process? I'm running (IMO) a > balanced config, but there's always room for improvement. Its that oddball > query that comes around once every so often that causes the problem. You can basically renice the process that is performing the query. See 'man nice' for details. Regards Gaetano Mendola