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@xxxxxxxxxxxxxx
[mailto:pgsql-admin-owner@xxxxxxxxxxxxxx] On Behalf Of Kevin Keith
Sent: Wednesday, April 05, 2006 11:14 AM
To: pgsql-admin@xxxxxxxxxxxxxx
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@xxxxxxxxxxxxx
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
