X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 3B8C19DC9C3 for ; Thu, 16 Mar 2006 14:17:27 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 68014-09 for ; Thu, 16 Mar 2006 14:17:26 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 2F9D49DC98E for ; Thu, 16 Mar 2006 14:17:23 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id k2GIHMdd018503; Thu, 16 Mar 2006 13:17:23 -0500 (EST) To: Jerry Sievers cc: pgsql-admin@postgresql.org Subject: Re: Curious run-away index build on upgrade to 8.1.3 In-reply-to: References: <16725.1142523155@sss.pgh.pa.us> Comments: In-reply-to Jerry Sievers message dated "16 Mar 2006 11:00:10 -0500" Date: Thu, 16 Mar 2006 13:17:22 -0500 Message-ID: <18502.1142533042@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.113 required=5 tests=[AWL=0.113] X-Spam-Score: 0.113 X-Spam-Level: X-Archive-Number: 200603/138 X-Sequence-Number: 20895 Jerry Sievers writes: > Platform is Solaris 2.9 I think this might be the key... I can reproduce an unreasonably long runtime if I use src/port/qsort.c (as we do on Solaris), but not with glibc's version of qsort. I think you are seeing the poor-choice-of-qsort-pivots problem recently discussed on -hackers: http://archives.postgresql.org/pgsql-hackers/2006-02/msg00590.php The fact that the data contains a very large fraction of nulls probably contributes to the problem (thanks for sending it BTW). The reason you only see it with maintenance_work_mem >= 64M is that below that, the problem doesn't fit into work_mem and so we don't use qsort at all. What I still don't understand though is why you see it in 8.1 and not 8.0 ... the src/port/qsort.c code didn't change at all between those versions. Maybe 8.0 isn't taking the qsort code path, perhaps because it uses a shade more memory or some such. Could you try increasing maintenance_work_mem even more, like to 100M, and see if 8.0 gets slow? regards, tom lane