Re: VLDB Features

Neil Conway <neilc@samurai.com>

From: Neil Conway <neilc@samurai.com>

To: Greg Smith <gsmith@gregsmith.com>

Cc: Josh Berkus <josh@agliodbs.com>, pgsql-hackers@postgresql.org

Date: 2007-12-16T06:07:46Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

doc: Fix COPY ON_ERROR option syntax synopsis.
- f6f8ac8e75c9 17.0 landed
Disallow specifying ON_ERROR option without value.
- a6d0fa5ef840 17.0 landed
Rename COPY option from SAVE_ERROR_TO to ON_ERROR
- b725b7eec431 17.0 landed
Fix spelling in notice
- 58fbbc9d683c 17.0 landed
Add new COPY option SAVE_ERROR_TO
- 9e2d8701194f 17.0 landed

On Tue, 2007-12-11 at 19:11 -0500, Greg Smith wrote:
> I'm curious what you feel is missing that pgloader doesn't fill that 
> requirement:  http://pgfoundry.org/projects/pgloader/

For complicated ETL, I agree that using an external tool makes the most
sense. But I think there is still merit in adding support to COPY for
the simple case of trying to load a data file that has some corrupted,
invalid or duplicate records.

-Neil