pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jim Nasby <jnasby@pervasive.com>
To: Tomeh, Husam <htomeh@firstam.com>
Cc: Kevin Keith <kkeith@borderware.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Error Handling with COPY command
Date: Thu, 6 Apr 2006 22:06:45 -0400
Message-ID: <09EE80C7-3209-4C81-BCE1-4D7264DD7ABB@pervasive.com> (raw)
In-Reply-To: <CB0FB369FF86E248A884BCC002562BCB010C0CF3@pisgsna01sxch01.ana.firstamdata.com>
References: <CB0FB369FF86E248A884BCC002562BCB010C0CF3@pisgsna01sxch01.ana.firstamdata.com>

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





view thread (3+ messages)

Message-ID: <09EE80C7-3209-4C81-BCE1-4D7264DD7ABB@pervasive.com>
Permalink:  ../09EE80C7-3209-4C81-BCE1-4D7264DD7ABB@pervasive.com/
Also on:    postgresql.org/message-id/09EE80C7-3209-4C81-BCE1-4D7264DD7ABB@pervasive.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: jnasby@pervasive.com, htomeh@firstam.com, kkeith@borderware.com
  Subject: Re: Error Handling with COPY command
  In-Reply-To: <09EE80C7-3209-4C81-BCE1-4D7264DD7ABB@pervasive.com>
  References: <CB0FB369FF86E248A884BCC002562BCB010C0CF3@pisgsna01sxch01.ana.firstamdata.com> <09EE80C7-3209-4C81-BCE1-4D7264DD7ABB@pervasive.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox