Re: PQputCopyData dont signal error - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: PQputCopyData dont signal error
Date
Msg-id CAB7nPqQt2iC-irsBPpAGsko+KXkgXXP9tTgtTZDUcOt7NJzujw@mail.gmail.com
Whole thread Raw
In response to Re: PQputCopyData dont signal error  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
On Tue, Apr 1, 2014 at 1:33 AM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> steve k wrote:
>
>> I am examining other ways to do mass inserts/writes that allow for
>> notification if some of the data contained within for some reason fails to
>> copy/insert so that the cause of the bad data can be examined and remedied
>> as soon as it occurs as well as writing the offending data to a log so that
>> not all of it is lost.
>
> Have you looked at PGLoader?
> https://github.com/dimitri/pgloader
Or pg_bulkload? It does exactly what you are looking for, aka
filtering rows that failed with COPY, on top of other things.
http://pgbulkload.projects.pgfoundry.org/pg_bulkload.html
-- 
Michael



pgsql-hackers by date:

Previous
From: Fabrízio de Royes Mello
Date:
Subject: Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements
Next
From: Jeff Janes
Date:
Subject: Re: Archive recovery won't be completed on some situation.