Error Handling with COPY command

From: Kevin Keith <kkeith(at)borderware(dot)com>
To: pgsql-admin(at)postgresql(dot)org
Subject: Error Handling with COPY command
Date: 2006-04-05 18:14:18
Message-ID: 443408FA.9000607@borderware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

Browse pgsql-admin by date

  From Date Subject
Next Message Rosser Schwarz 2006-04-05 18:26:13 Re: PITR Based replication ...
Previous Message Marc G. Fournier 2006-04-05 15:53:35 Re: PITR Based replication ...