X-Original-To: pgsql-performance@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 74AF7475A71 for ; Fri, 21 Feb 2003 10:48:06 -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-02 for ; Fri, 21 Feb 2003 10:47:55 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 8C993475C26 for ; Fri, 21 Feb 2003 10:45:00 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1LFj35u015035; Fri, 21 Feb 2003 10:45:03 -0500 (EST) To: Kevin White Cc: pgsql-performance@postgresql.org Subject: Re: Really bad insert performance: what did I do wrong? In-reply-to: <3E564695.7030906@digital-ics.com> References: <3E564695.7030906@digital-ics.com> Comments: In-reply-to Kevin White message dated "Fri, 21 Feb 2003 10:32:37 -0500" Date: Fri, 21 Feb 2003 10:45:03 -0500 Message-ID: <15034.1045842303@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new X-Archive-Number: 200302/153 X-Sequence-Number: 1209 Kevin White writes: > My box, however, isn't a production server, so I attempted to create the > database again on a Sun Blade: > ... > It took almost 2 days to load the table on this box. 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. regards, tom lane