From: Kevin Keith <kkeith@borderware.com>
To: pgsql-admin@postgresql.org
Subject: Error Handling with COPY command
Date: Wed, 05 Apr 2006 14:14:18 -0400
Message-ID: <443408FA.9000607@borderware.com> (raw)
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
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: kkeith@borderware.com
Subject: Re: Error Handling with COPY command
In-Reply-To: <443408FA.9000607@borderware.com>
References: <443408FA.9000607@borderware.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