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 0771652831 for ; Fri, 24 Jun 2005 11:43:51 -0300 (ADT) 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 61730-05 for ; Fri, 24 Jun 2005 14:43:47 +0000 (GMT) Received: from koolancexeon.g2switchworks.com (mail.g2switchworks.com [63.87.162.25]) by svr1.postgresql.org (Postfix) with ESMTP id BED1A5280C for ; Fri, 24 Jun 2005 11:43:44 -0300 (ADT) Received: mail.g2switchworks.com 10.10.1.8 from 10.10.1.37 10.10.1.37 via HTTP with MS-WebStorage 6.5.6944 Received: from state.g2switchworks.com by mail.g2switchworks.com; 24 Jun 2005 09:43:43 -0500 Subject: Re: psql copy errors From: Scott Marlowe To: ljh1469@alibaba-inc.com Cc: "David.Bear@asu.edu" , pgsql-admin In-Reply-To: <20050624055243.3B13566C13B@smtp-hz> References: <20050624055243.3B13566C13B@smtp-hz> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Message-Id: <1119624222.8208.67.camel@state.g2switchworks.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 24 Jun 2005 09:43:43 -0500 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.005 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200506/197 X-Sequence-Number: 17952 On Fri, 2005-06-24 at 00:52, =E6=9D=8E=E6=B1=9F=E5=8D=8E wrote: > David Bear: >=20 > Yes. I agree with you. > \copy is really too brittle. > I wonder why \copy is not like oracle's sqlldr? > I think sqlldr is more powerful. When using sqlldr,we can specify= the maximum error records we allow,and we can also specify the number we s= hould commit in every transaction. While I wouldn't mind have the versatility of sqlldr, I would HATE to have to deal with such a clunky interface. The only features of sqlldr I actually like are the ones that allow rejected records to go into a separate file. But like most of oracle's tools, it's awkward to use, and requires a lot of up front work even if you only want a simple load. Sure, add some features to \copy, but don't emulate the WAY those features are implemented oracle. > Another aspect is also important. Oracle has better partition tabl= e facilities,it's especially suitable for large tables,as well as index par= tition concepts.But PostgreSQL has no such concepts.These are really import= ant for large database. No one would complain if someone stepped up and programmed a decent table partitioning patch. I have a feeling it's one of the things on the TODO list that will happen in the next version or two.