2010/10/5 Konstantin Izmailov <pgfizm@xxxxxxxxx>: > Let me ask another question related to the INSERT as well. I'm running > periodic import into Postgres and sometimes the application tries to insert > a duplicate row which, as expected, results in "integrity violation" error. > This aborts entire transaction (which is huge). I can use "SAVEPOINT > ...;INSERT ...;RELEASE SAVEPOINT ..." but I'm concerned with potential > performance hit. I haven't had time to benchmark the difference in > performance, so could you please suggest if the difference will be > noticeable. Is there a better approach? Is it possible to customize INSERT > behavior to not abort transaction due to an integrity violation? Would it be > possible to alter COPY command behavior as well (to gracefully continue > after integrity violation)? you probably want pgloader : http://pgloader.projects.postgresql.org/ -- Cédric Villemain 2ndQuadrant http://2ndQuadrant.fr/ ; PostgreSQL : Expertise, Formation et Support -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
