Re: [Sqlgrey-users] Odd characters causing db crash

[Kenneth M. <kt...@ri...>]

On Thu, Jan 20, 2011 at 07:06:43AM +0000, Steve Heaven wrote:
> Early this morning our Postgres db crashed and restarted several times.
> In the logs I found this:
> 
> Jan 20 03:43:53 frigga sqlgrey: grey: from awl match: updating
> 71.81.141.83(71.81.141.83),
> s???nc...@18...(s???nc...@18...) 
> Jan 20 03:43:53 frigga sqlgrey: dbaccess: warning: couldn't do query:
> UPDATE from_awl SET last_seen = NOW(), first_seen = first_seen WHERE
> sender_name = 's???nchez85' AND sender_domain = '1800hurt911.com' AND src
> = '71.81.141.83': ERROR:  invalid byte sequence for encoding "UTF8":
> 0xe16e63 HINT:  This error can also happen if the byte sequence does not
> match the encoding expected by the server, which is controlled by
> "client_encoding". , reconnecting to DB 
> Jan 20 03:43:53 frigga sqlgrey: warning: Use of uninitialized value in
> concatenation (.) or string at /usr/sbin/sqlgrey line 1154. 
> Jan 20 03:43:53 frigga sqlgrey: dbaccess: error: couldn't access
> from_awl table:  
> 
> It looks like it crashed because the email address had a non UTF8
> character. What should the 'client_encoding' be set to?
> 
> We are running  sqlgrey 1.7.6 and postgresql  8.1.11
> 
> Thanks
> 
> Steve
> 

You will need to use SQL_ASCII or C encoding for the database
in initdb. Been there, done that, have the crash dump... :)

Ken