X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 7CB3F329E69 for ; Fri, 24 Sep 2004 21:59:46 +0100 (BST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 19670-07 for ; Fri, 24 Sep 2004 20:59:35 +0000 (GMT) Received: from mproxy.gmail.com (rproxy.gmail.com [64.233.170.201]) by svr1.postgresql.org (Postfix) with ESMTP id 38871329E54 for ; Fri, 24 Sep 2004 21:59:34 +0100 (BST) Received: by mproxy.gmail.com with SMTP id 73so2369653rnk for ; Fri, 24 Sep 2004 13:57:49 -0700 (PDT) Received: by 10.38.208.40 with SMTP id f40mr1416862rng; Fri, 24 Sep 2004 13:57:46 -0700 (PDT) Received: by 10.38.76.43 with HTTP; Fri, 24 Sep 2004 13:57:46 -0700 (PDT) Message-ID: <37d451f704092413573a5ea4e0@mail.gmail.com> Date: Fri, 24 Sep 2004 15:57:46 -0500 From: Rosser Schwarz Reply-To: Rosser Schwarz To: "Goulet, Dick" Subject: Re: Porting from MS SQL Server to PostGres Cc: pwbyrne@hotmail.com, pgsql-admin@postgresql.org In-Reply-To: <4001DEAF7DF9BD498B58B45051FBEA650146C760@25exch1.vicorpower.vicr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <4001DEAF7DF9BD498B58B45051FBEA650146C760@25exch1.vicorpower.vicr.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200409/233 X-Sequence-Number: 14936 while you weren't looking, Goulet, Dick wrote: > I'd precreate all of the tables/indexes and then move the data... If you have a lot of data, it's probably better to punt on creating the indices until after you've moved the data. Bulk populating indexed tables, particularly if the table has more than just the primary key index, can be awfully slow. At one point, we tried dumping several million tuples into a table with a dozen-odd indices. Only did that once. /rls -- :wq