Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id B75CE9FBCD1 for ; Wed, 2 May 2007 12:32:02 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-maia, port 10024) with ESMTP id 52139-01 for ; Wed, 2 May 2007 12:32:00 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from exchange.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by postgresql.org (Postfix) with ESMTP id EBAC79FBBDB for ; Wed, 2 May 2007 12:31:59 -0300 (ADT) Received: from 10.10.1.37 ([10.10.1.37]) by exchange.g2switchworks.com ([10.10.1.2]) with Microsoft Exchange Server HTTP-DAV ; Wed, 2 May 2007 15:31:59 +0000 Received: from state.g2switchworks.com by mail.g2switchworks.com; 02 May 2007 10:31:59 -0500 Subject: Re: reindexdb hangs From: Scott Marlowe To: dx k9 Cc: pgsql-admin@postgresql.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1178119918.2953.5.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Wed, 02 May 2007 10:31:59 -0500 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200705/21 X-Sequence-Number: 25341 On Wed, 2007-05-02 at 09:50, dx k9 wrote: > Hi, > > What would cause or what should I do with a table that hangs during its > reindexing? I can see in the messages the last table to reindex, so > sequentially the next table must be the problem. > I have statement_timeout set for 6 hours, then I get "canceling statement > due to statement timeout" Ok, that's fine, and I don't think setting the > statement_timeout to 0 will really help. The question is why did it hang or > what are some reasons that would make a table hang a reindexing? And is > there a solution? The real question is did it hang? If the machine was still working on reindexing then it wasn't hung, it was just taking longer than you wanted it to. Which can also be a problem, but isn't the same thing as hanging, and as it's a different problem, would have a different solution than if it is hanging. So, what does vmstat / top / iostat have to say about this "hang"? Was it really hanging, or just taking a long time?