On 29/11/11 14:53, Sven wrote: > Hi > > I'm getting errors such as the following logged on a virgin install of the > above > versions: > > [11/29/2011 14:29:00] 29154: ERROR: invalid byte sequence for encoding > "UTF8": > 0xae: INSERT INTO dspam_signature_data (uid,signature,length,created_on,data) > VALUES (1,E'4ed4de1c291545272412566',752,CURRENT_DATE,E'\xae7c566c2052851801 > 00000000000000bf80774b2dadefd301 ... ') >
Hi Sven, There was a thread on this mailing list a few days/weeks ago about incompatibility between dspam 3.10 and postgres 9.1. The workaround is to set standard_conforming_strings=off in postgresql.conf, downgrade to postgresql 9.0, or wait until dspam 3.10.2 is released, which will contain a fix for this issue. -- Tom ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
