We have a process which inserts a number of records into a very
large table, and which relies on the presence of a unique index to keep
it from inserting something that's already there. Presently, the process
just does the insert for each row, and detects the constraint violation
to see if the insert failed.
However, this goes on all day, and the log is rapidly filling with
2001-11-09 13:40:59 [2280] ERROR: Cannot insert a duplicate key
into unique index ix_links_2
over and over. Is there a way for the backend, or the process doing the
insert, to suppress this message? It really doesn't inform us of
anything, and it's chewing up resources.
--
Jeff Boes vox 616.226.9550
Database Engineer fax 616.349.9076
Nexcerpt, Inc. jboes@nexcerpt.com
