>>>>> "HH" == Hanno Hirschberger <hannohirschber...@googlemail.com> writes:
HH> ERROR: duplicate key value violates unique constraint HH> "dspam_token_data_uid_token_key" Instead of using a SELECT to check whether the key exists, dspam's sql just attempts to insert a new row and, if that fails, updates the existing row instead. Look at pgsql_drv.c line 1120 or so. That it creates noise in the pg logs is annoying. Perhaps if it were re-done as a single query, with the update if cannot insert logic all in sql (or pgsql), it might avoid the error logging??? -JimC -- James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6 ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
