>
>
>Adding options to the COPY command is no help either, because the COPY
>may be embedded in a multi-gigabyte dump file that you can't edit
>conveniently. (And what of pg_restore, or other applications that
>generate COPY commands?) My approach of using a GUC variable is better
>because it can be set from outside the dump script --- in
>postgresql.conf, if necessary.
Speaking of COPY, is there a way to tell copy not to barf on errors (and
set how many errors are acceptable)?
Can I tell copy to commit every X rows?
--
Naomi Walker
Chief Information Officer
Eldorado Computing, Inc.
602-604-3100 ext 242