> Just to clarify, 8.2 was a little weird regarding encoding. It was more
> strict in some contexts, but there were still ways to get invalid byte
> sequences inserted, and after the bad data was there, you couldn't COPY
> the data (dump/restore wouldn't work). That could also explain his
> problems.
> 
  Does that mean there is a way I can force Slony to insert the data and
ignore the error?



> I'm not entirely sure this is his problem, however, because he said he
> could dump/restore. Maybe he's just got different server encodings?
> 
  Yeah I could dump the data on the Master then insert it into the Slave
without any issues. Initially, I considered the process by which data was
been inserted into the table but since I could dump & insert, I then
expected that the function/method inserting data was inserting a character
that was not in UTF-8 format but then how come it was not rectified by the
"SET client_encoding" command?
  Really I need help....cos I've been thinking about it throughout the night
and I don't want to reinstall the postgresql on the Slave again.....it was
not a very sweet experience when I first did it.

   Regards........Victor


-- 
View this message in context: http://www.nabble.com/UTF-8-encoding-Error-tp16000710p16023404.html
Sent from the Slony-I -- General mailing list archive at Nabble.com.