Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TxOfG-00049b-F6 for pgsql-performance@arkaria.postgresql.org; Mon, 21 Jan 2013 21:12:22 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.72) (envelope-from ) id 1TxOfF-0006yl-Tl for pgsql-performance@arkaria.postgresql.org; Mon, 21 Jan 2013 21:12:21 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TxOfD-0006xV-W6 for pgsql-performance@postgresql.org; Mon, 21 Jan 2013 21:12:20 +0000 Received: from mout.gmx.net ([74.208.4.201]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TxOfC-00074T-6v for pgsql-performance@postgresql.org; Mon, 21 Jan 2013 21:12:19 +0000 Received: from mailout-us.gmx.com ([172.19.198.45]) by mrigmx.server.lan (mrigmxus002) with ESMTP (Nemesis) id 0LpvxT-1TIqZy06Mh-00flRI for ; Mon, 21 Jan 2013 22:12:17 +0100 Received: (qmail 8170 invoked by uid 0); 21 Jan 2013 21:12:16 -0000 Received: from 76.255.19.161 by rms-us005 with HTTP Cc: pgsql-performance@postgresql.org Content-Type: text/plain; charset="utf-8" Date: Mon, 21 Jan 2013 16:12:14 -0500 From: "Kevin Grittner" Message-ID: <20130121211214.120610@gmx.com> MIME-Version: 1.0 Subject: Re: High CPU usage after partitioning To: "Merlin Moncure" ,"rudi" X-Authenticated: #138763884 X-Flags: 0001 X-Mailer: GMX.com Web Mailer x-registered: 0 Content-Transfer-Encoding: 8bit X-GMX-UID: ecqPcHlO3zOlOQ09Lnwhx8h+IGRvb8BI 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 Merlin Moncure wrote: >> I'm running postgresl 9.0. After partitioning a big table, CPU >> usage raised from average 5-10% to average 70-80%. > First thing that jumps to mind is you have some seq-scan heavy > plans that were not seq-scan before. Make sure that all indexes are defined for each partition. It is not enough to define them on just the parent level. -Kevin -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance