Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Yyndl-0000fp-Ol for pgsql-performance@arkaria.postgresql.org; Sat, 30 May 2015 20:45:57 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Yyndk-0006ju-FS for pgsql-performance@arkaria.postgresql.org; Sat, 30 May 2015 20:45:56 +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 1Yyndj-0006jn-Av for pgsql-performance@postgresql.org; Sat, 30 May 2015 20:45:55 +0000 Received: from mail-wi0-f174.google.com ([209.85.212.174]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1Yyndg-0006tf-8Y for pgsql-performance@postgresql.org; Sat, 30 May 2015 20:45:53 +0000 Received: by wizo1 with SMTP id o1so61371004wiz.1 for ; Sat, 30 May 2015 13:45:50 -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=TRpvm0i9Ye9cSxDCsSm5iCfTKsq6LMNrLC3qzr3eBh4=; b=R3JWZW3JJtPMyduA5jRX1eEV8XGkt0JQHr/RlmMvbJgHvyOkgeTlgkKAAiM994J0/t SYci1NCSa8eSgj9CukXwF+ztuxcccdPdE0W7WFY2rgy0Hxr1vCOF/9TzFQCN7HXDtvg/ GcKcJWzZonB6likbtXgUfsGk0kv1+EAXDfFcm4k2e3F25LnJcpidwby7QEBWOFrKoW8C Vpm+JM1PvRU86FPnBG76bfuoa3U2Ydh7IiUT9o4iCL/q+siYAfq4rco/ahfILhVNeT++ bAM7auFn9zbHYCl1wG9qPQxUhNXRXtMVzOAocTjNYzuQ720NPBJT/HzoI6cDC6tG7WYB zHfQ== X-Gm-Message-State: ALoCoQnGd0CGxKpfreLxhY4w+3f90RBTrWISz3+bBO5r4NWzlttqhHjzGbI3U3WPpprdbkqwBgqVzz4p3NaYlYmkZq57RfBknLoGYL25S/O2piyBHf4FFNDDH8VwZn3oQdqca7a55p0xeeDCpEDe2T+/dIO4rpPAEmIfVDMKIzLM6OvJyWRh7M9jwU2Ar7uIG67xJuleOI9OaZ72yhN1Zdkgb1UiNJwulg== X-Received: by 10.180.76.8 with SMTP id g8mr7057077wiw.79.1433018750002; Sat, 30 May 2015 13:45:50 -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 l6sm14261213wjz.4.2015.05.30.13.45.48 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 30 May 2015 13:45:49 -0700 (PDT) Message-ID: <556A2179.3030809@2ndquadrant.com> Date: Sat, 30 May 2015 22:45:45 +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-performance@postgresql.org Subject: Re: Postmaster eating up all my cpu References: <1432812350946-5851428.post@n5.nabble.com> In-Reply-To: <1432812350946-5851428.post@n5.nabble.com> Content-Type: text/plain; charset=windows-1252; 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-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Hi, On 05/28/15 13:25, birimblongas wrote: > Hi, > > My app was working just fine. A month ago postmaster started to eat all my > cpu sometimes (not all day, but a lot of times and everyday) and then my app > gets really slow and sometimes don't even complete the requests. > > What could it be? A lot of things. The first step should be looking at pg_stat_activity, what is the process eating the CPU doing. We also need much more information about your system - what PostgreSQL version are you using, what kind of OS, configuration etc. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance