X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id CF2149F944D for ; Sat, 6 May 2006 22:34:55 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 10535-05 for ; Sat, 6 May 2006 22:34:41 -0300 (ADT) X-Greylist: delayed 00:18:38.204614 by SQLgrey- Received: from mta5.adelphia.net (mta5.adelphia.net [68.168.78.187]) by postgresql.org (Postfix) with ESMTP id EB7909FA4DE for ; Sat, 6 May 2006 22:34:41 -0300 (ADT) Received: from [10.1.2.102] (really [70.33.56.85]) by mta13.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20060507011601.XUFQ27153.mta13.adelphia.net@[10.1.2.102]> for ; Sat, 6 May 2006 21:16:01 -0400 From: "Ed L." To: "pgsql-performance@postgresql.org" Subject: pg_dump index creation order Date: Sat, 6 May 2006 19:15:55 -0600 User-Agent: KMail/1.8.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200605061915.55712.pgsql@bluepolka.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200605/126 X-Sequence-Number: 18913 I'm watching a long, painfully slow 60GB load from pg_dump (8.1.2), and noticing it's jumping back and forth from different tables. I assume this is the index creation order showing up. Would it make more sense to have pg_dump dump indexes grouped by the table? That way, if a table got loaded into cache for one index creation, it might still be there for the immediatly following index creations on the same table... Ed