| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | steve k <steven(dot)c(dot)kohler(at)nasa(dot)gov>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PQputCopyData dont signal error |
| Date: | 2014-04-01 04:36:48 |
| Message-ID: | CAB7nPqQt2iC-irsBPpAGsko+KXkgXXP9tTgtTZDUcOt7NJzujw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Apr 1, 2014 at 1:33 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2014-04-01 04:39:33 | Re: Archive recovery won't be completed on some situation. |
| Previous Message | Stephen Frost | 2014-04-01 04:34:34 | Re: Patch to add support of "IF NOT EXISTS" to others "CREATE" statements |