Joseph S wrote:
> Steve Singer wrote:
>> Joseph S wrote:
>>
>>> I'm not sure how to do that. I think the multiple updates are done in 
>>> one statement and I'm not sure how to figure out which one slony is 
>>> trying when it gets the error.
>>
>> Can you find this out from the postgresql log on the replica?  You can 
>> get it to print the SQL statement that caused the error.
> 
> For other errors it puts the statement in the log right after the ERROR 
> line, but not for encoding errors.

Is turning in statement logging (so you log all queries, then see the 
last one that worked to determine what the  next row from sl_log_x  is) 
an option?



> 
> ERROR:  invalid byte sequence for encoding "UTF8": 0x98
> 
> 
> 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".
> ERROR:  invalid byte sequence for encoding "UTF8": 0x98
> 
> 
> 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".
> ERROR:  invalid byte sequence for encoding "UTF8": 0xb0
> 
> 
> 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".
> ERROR:  invalid byte sequence for encoding "UTF8": 0xb0
> 
> 
> 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".
>>
>>
>>
> 


-- 
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142