Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WQdSS-0001a1-Ht for pgsql-performance@arkaria.postgresql.org; Thu, 20 Mar 2014 13:56:32 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WQdSS-0000UR-2Y for pgsql-performance@arkaria.postgresql.org; Thu, 20 Mar 2014 13:56:32 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WQdSR-0000UE-51 for pgsql-performance@postgresql.org; Thu, 20 Mar 2014 13:56:31 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WQdSN-0004Qu-VQ for pgsql-performance@postgresql.org; Thu, 20 Mar 2014 13:56:30 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id s2KDuPr5002043; Thu, 20 Mar 2014 09:56:25 -0400 From: Tom Lane To: Franck Routier cc: pgsql-performance@postgresql.org Subject: Re: long lasting select, no io nor cpu usage ? In-reply-to: <532AF271.4040903@axege.com> References: <532AF271.4040903@axege.com> Comments: In-reply-to Franck Routier message dated "Thu, 20 Mar 2014 14:51:45 +0100" Date: Thu, 20 Mar 2014 09:56:25 -0400 Message-ID: <2042.1395323785@sss.pgh.pa.us> X-Pg-Spam-Score: -1.9 (-) 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 Franck Routier writes: > I am doing a select, that did not finish after some 15 hours... Select > is as follows: > select * from sanact where sanact___rfovsnide = 'MYVERSION' order by > sanactcsu; > There is an index on sanact___rfovsnide and doing EXPLAIN shows it is used. > Resulting dataset should be 1626000 rows. > iostat shows 99.5% idle disks, almost no activity. > top shows almost no cpu usage. > Where should I be looking for a problem ? pg_locks, probably. regards, tom lane -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance