On Sun, May 16, 2010 at 12:38 PM, Mark Fenbers <Mark(dot)Fenbers(at)noaa(dot)gov> wrote:
> I am using psql's \copy command to add records to a database from a file.
> The file has over 100,000 lines. Occasionally, there is a duplicate, and
> the import ceases and an internal rollback is performed. In other words, no
> data is imported even if the first error occurs near the end of the file.
> I am looking for an option/switch to tell psql (or the \copy command) to
> skip over any duplicate key constraint viloations and continue to load any
> data that doesn't violate a duplicate key constraint. Is there such an
Sounds like you want this:
Note that copy is optimized to work in a single transaction. Breaking
those semantics WILL result in a slow load time, and there's not much
you can do about that.
In response to
pgsql-sql by date
|Next:||From: Torsten Zühlsdorff||Date: 2010-05-17 08:57:08|
|Subject: Re: [Trigger] Help needed with NEW.* and TG_TABLE_NAME|
|Previous:||From: Tim Landscheidt||Date: 2010-05-17 00:32:00|
|Subject: Re: import ignoring duplicates|