X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 778D94758E6 for ; Fri, 21 Feb 2003 10:48:50 -0500 (EST) Received: from postgresql.org ([64.49.215.8]) by localhost (postgresql.org [64.49.215.8:10024]) (amavisd-new) with SMTP id 08951-04 for ; Fri, 21 Feb 2003 10:48:39 -0500 (EST) Received: from maverick.digital-ics.com (maverick.digital-ics.com [63.239.101.196]) by postgresql.org (Postfix) with ESMTP id 0CFBE475B47 for ; Fri, 21 Feb 2003 10:47:14 -0500 (EST) Received: from digital-ics.com (gremlin.ics.digital-ics.com [192.168.2.52]) by maverick.digital-ics.com (8.12.6/8.12.6) with ESMTP id h1LFlIhm000978; Fri, 21 Feb 2003 10:47:18 -0500 (EST) Message-ID: <3E564A06.8070809@digital-ics.com> Date: Fri, 21 Feb 2003 10:47:18 -0500 From: Kevin White User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-performance@postgresql.org Subject: Re: Really bad insert performance: what did I do wrong? References: <3E564695.7030906@digital-ics.com> <15034.1045842303@sss.pgh.pa.us> In-Reply-To: <15034.1045842303@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/152 X-Sequence-Number: 1208 > Yipes. We found awhile ago that Solaris' standard qsort() really sucks, > but 7.3 should work around that --- and I don't think qsort would be > invoked during data load anyway. > > Do you want to rebuild Postgres with profiling enabled, and get a gprof > trace so we can see where the time is going? You don't need to run it > for two days --- a few minutes' worth of runtime should be plenty. Great...I'd love to...as I've never had a problem with Postgres like this, I didn't even know where to start...I'll look for how to do that. Kevin