Received: from maia.hub.org (maia-5.hub.org [200.46.204.29]) by mail.postgresql.org (Postfix) with ESMTP id E53451337B61 for ; Wed, 26 Jan 2011 16:13:18 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024) with ESMTP id 61290-10 for ; Wed, 26 Jan 2011 20:13:12 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by mail.postgresql.org (Postfix) with ESMTP id 73532133655C for ; Wed, 26 Jan 2011 16:13:11 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id p0QKD29E024467; Wed, 26 Jan 2011 15:13:02 -0500 (EST) To: Josh Berkus cc: pgsql-bugs@postgresql.org Subject: Re: Multicolun index creation never completes on 9.0.1/solaris In-reply-to: <4D40795A.8000103@agliodbs.com> References: <4D3F2D10.1020905@agliodbs.com> <21735.1295990515@sss.pgh.pa.us> <4D3F86D9.9080200@agliodbs.com> <14452.1296010153@sss.pgh.pa.us> <4D4069EF.6040603@agliodbs.com> <23139.1296069017@sss.pgh.pa.us> <4D40795A.8000103@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Wed, 26 Jan 2011 11:43:22 -0800" Date: Wed, 26 Jan 2011 15:13:02 -0500 Message-ID: <24466.1296072782@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.91 tagged_above=-5 required=5 tests=BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 X-Spam-Level: X-Archive-Number: 201101/216 X-Sequence-Number: 29238 Josh Berkus writes: > Oh! Actually, it only *did* 27 runs. So it actually completed building > the index. I'd expected trace_sort to give me some kind of completion > message; apologies for not checking all screen windows. Huh, there should be an "external sort ended" message, as well as some other ones once it finishes writing the initial runs. > So, why didn't the index build complete (after more than 36 hours) when > I ran it as part of pg_restore? I guess this goes back to being a > pg_restore problem and not an index build problem. First thing that comes to mind is to wonder what maintenance_work_mem setting was in effect for the pg_restore run. regards, tom lane