X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6B95111F6C77 for ; Fri, 7 Apr 2006 01:38:44 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 73002-10-2 for ; Fri, 7 Apr 2006 01:38:41 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id DEC8B11F621C for ; Fri, 7 Apr 2006 01:38:40 -0300 (ADT) Received: from [192.168.42.113] (natpool.bovine.net [67.100.216.14]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by noel.decibel.org (Postfix) with ESMTP id BCA5156440; Thu, 6 Apr 2006 23:38:40 -0500 (CDT) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <09EE80C7-3209-4C81-BCE1-4D7264DD7ABB@pervasive.com> Cc: "Kevin Keith" , pgsql-admin@postgresql.org Content-Transfer-Encoding: 7bit From: Jim Nasby Subject: Re: Error Handling with COPY command Date: Thu, 6 Apr 2006 22:06:45 -0400 To: "Tomeh, Husam" X-Mailer: Apple Mail (2.746.3) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=4.706 required=5 tests=[AWL=-4.011, RAZOR2_CF_RANGE_51_100=0.5, RAZOR2_CF_RANGE_E8_51_100=1.5, RAZOR2_CHECK=0.5, URIBL_OB_SURBL=2.617, URIBL_SC_SURBL=3.6] X-Spam-Score: 4.706 X-Spam-Level: **** X-Archive-Number: 200604/69 X-Sequence-Number: 21238 In the meantime, there is a replacement for COPY on pgFoundry. I think it's called pgloader... On Apr 5, 2006, at 6:42 PM, Tomeh, Husam wrote: > I think that's still on the TODO list. A very useful feature that I've > looking forward to as well. > > http://www.postgresql.org/docs/faqs.TODO.html > > ---- > > Husam > http://two.fsphost.com/rdbms > > > -----Original Message----- > From: pgsql-admin-owner@postgresql.org > [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Kevin Keith > Sent: Wednesday, April 05, 2006 11:14 AM > To: pgsql-admin@postgresql.org > Subject: [ADMIN] Error Handling with COPY command > > I was wondering if anything has been implemented or is in the works > in a > > future version - where when provided setting / flag / max number of > errors - the COPY command would not fail on the error and continue > loading data. It would then put the data that didn't load due to error > in another location (i.e. an error data file, or an error table). When > performing bulk data loads, it would be useful to have this type of > feature, and avoid the need to vacuum the table after a large data > load > quits due to one error. > > I have worked with Oracle in the past, and it has a similar feature > the > SQL Loader. A threshold is set to x, and it will only stop after x > number of errors were encountered. > > I have seen a few threads on this subject - I was wondering if this > is / > > will be included in a future version, or whether the concept is dead > because of its potential risks (i.e. the COPY command would be told to > ignore errors and continue). > > Thanks, > Kevin > > ---------------------------(end of > broadcast)--------------------------- > TIP 6: explain analyze is your friend > ********************************************************************** > This message contains confidential information intended only for > the use of the addressee(s) named above and may contain information > that is legally privileged. If you are not the addressee, or the > person responsible for delivering it to the addressee, you are > hereby notified that reading, disseminating, distributing or > copying this message is strictly prohibited. If you have received > this message by mistake, please immediately notify us by replying > to the message and delete the original message immediately thereafter. > > Thank you. > > FADLD Tag > ********************************************************************** > > > ---------------------------(end of > broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461