Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YyNvW-00038B-9A for pgsql-bugs@arkaria.postgresql.org; Fri, 29 May 2015 17:18:34 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YyNvV-0004uX-Oz for pgsql-bugs@arkaria.postgresql.org; Fri, 29 May 2015 17:18:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YyNvU-0004t8-Jo for pgsql-bugs@postgresql.org; Fri, 29 May 2015 17:18:32 +0000 Received: from mail-wg0-f45.google.com ([74.125.82.45]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1YyNvQ-0000N4-Dk for pgsql-bugs@postgresql.org; Fri, 29 May 2015 17:18:31 +0000 Received: by wgez8 with SMTP id z8so68236097wge.0 for ; Fri, 29 May 2015 10:18:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bu6DGieBg0oaXX5nW1dv050v41UV+wdxWOmJfyEY4+o=; b=Cs127l+bs0vQZtwuXRFgE4s7RWnPwz/zeB971c9GvU4s9lqXqQAoNY7MY1gQqrzCHc uihlDASRs8851g3eQhkyZ9Q8hqR2gh+STo052ScxI+4tUXjuuSXn5Loa7yiTyPnWnmxv 8nWBPkkNK/8NG6bQ/WI2EVhix4tvuxYMQh9A3Unr3NldzEgktnfFTc88ZAqjDgV7baj1 s9ERPbT99dX+7JSnB5dc6M7WmTGPXhDnmWxgv9hpBoeiA90TbBl8ptDbi0rzBP8xEa/x f59px3+nntjRQcAAtsVtYMZNJbR/kb8x7iglb4vW0LCmR7YcoDtm6otT+2AFOSghHNT0 iy/w== X-Gm-Message-State: ALoCoQkhxhWSbjkGfnrdmDW5ERh2ev/sTr/UrhjBobItjaV05cDdWJ9/yHJ2uzA/CoU3r962JLxt/Ogafwcr4PXgrWSx1ivceDZ0lmxkaWme0aLaf9v/aXbRrUuiNFbVPHswOVCsg6a3/WrJxSv9RzJ6pQvEqa4AEoSCDHvQuuYXR1G7jgBpr0M0Jz9NsoNExHnpB0pOWYf2 X-Received: by 10.180.73.230 with SMTP id o6mr8587676wiv.11.1432919906686; Fri, 29 May 2015 10:18:26 -0700 (PDT) Received: from [10.137.2.12] (ip-78-45-136-74.net.upcbroadband.cz. [78.45.136.74]) by mx.google.com with ESMTPSA id l6sm9241194wjz.4.2015.05.29.10.18.25 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 May 2015 10:18:26 -0700 (PDT) Message-ID: <55689F5E.8020808@2ndquadrant.com> Date: Fri, 29 May 2015 19:18:22 +0200 From: Tomas Vondra User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0 MIME-Version: 1.0 To: pgsql-bugs@postgresql.org Subject: Re: Postgres is using 100% CPU References: In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-bugs Precedence: bulk Sender: pgsql-bugs-owner@postgresql.org On 05/29/15 18:40, Ashik S L wrote: > Hi All, > > I am using postgresDB on redhat machine which is having 4GB RAM > machine. As soon as it starts to update the postgres DB it will reach > 100%cpu. It will comedown to normal after 40 minutes. I tried perform > some tuning on the postgres DB, But result was same.I am not postgres > DB expert. Even we are not seeing in all machine. Only few machines we > are seeing this issue. Any help on this would be appreciated. ... also, this is not a bug. This is clearly a performance question, so please post it to pgsql-performance list. -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs