Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YyNue-00035y-Od for pgsql-bugs@arkaria.postgresql.org; Fri, 29 May 2015 17:17:40 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YyNue-0003r4-73 for pgsql-bugs@arkaria.postgresql.org; Fri, 29 May 2015 17:17:40 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YyNud-0003pG-9Q for pgsql-bugs@postgresql.org; Fri, 29 May 2015 17:17:39 +0000 Received: from mail-wg0-f52.google.com ([74.125.82.52]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1YyNua-0001BZ-62 for pgsql-bugs@postgresql.org; Fri, 29 May 2015 17:17:38 +0000 Received: by wgv5 with SMTP id 5so68224777wgv.1 for ; Fri, 29 May 2015 10:17:34 -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=lGuRPv7+IwauBQAdLBdts67zrNiVel6QcLgoNfzWoJk=; b=Vd1tQ0lUYnCK88lDYoxI6eV0jGMPrHigyjQUK85GQ+NMKyZTEkz99LHJfFhcniwUDP MxO2U+djiUFF0EzIsBTStjykZQlUNvNHOnuFg651hPEjl/Uwv5UU3MPgy1qCJR46Qq7V b53jkE1hLhCOi+zkKrRQxBXODpdR3vkOImru61Oh0nIO/p8dMQDF3EDx/RNNmnO10D7K keB3PUqOv8aY5b3VOK0Q/XPtpMXl5AsmQpIvus7dI84s3X6MtXpGgdQc6N5ovXs88se+ I5jOfh1v5n7lrlu3VZEA1/Z6SrvJkEg3WNVBrm4EKvKEXkZo9+NAfdGWPfNUpSlU4Vu/ z+8Q== X-Gm-Message-State: ALoCoQkjX9jycgzlhs8aEOJameBIk7ROFmpD07lsOoNQjM/01CqlyW8SXi1fH8OrEumDZHUYXZRiZo3gK5HxmhO6E4FGzAKe/bwO78rAmd8iwtVIRiBl/Dc6RqqET5Hg3udGrSf45CKBZthhBw8BZF7x59Ch38ODuM6Y6iwhVVgJ9px2JKNrX/rEBQMeEGNvIyTU/vyj4mLA X-Received: by 10.194.121.38 with SMTP id lh6mr16890689wjb.2.1432919854310; Fri, 29 May 2015 10:17:34 -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 o5sm4661704wia.0.2015.05.29.10.17.32 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 29 May 2015 10:17:33 -0700 (PDT) Message-ID: <55689F29.3060104@2ndquadrant.com> Date: Fri, 29 May 2015 19:17:29 +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: -2.6 (--) 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 Hi, 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. We need to know more about what you mean by "update the postgres DB", and basic information like database size, PostgreSQL version etc. regards -- 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