[email protected] wrote:
> Slony replication between my two servers is failing with this:
>
> " ERROR: invalid byte sequence for encoding "UTF8": 0xac
> 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".
Can you determine where the value '0xac' comes from?
CREATE TABLE a(a text);
INSERT INTO a VALUES ('\xac');
on a UTF8 database fails. Does the data on your master actually contain
this in a text field or is the data being written into sl_log being
corrupted?
>
> Searching the archives has revealed that people have had this problem
> before, but the consensus was that the problem was caused by the two pg
> installations having different versions or different encodings. Both my
> servers are pg 8.4.3, encodings are UTF8, and slony is 2.0.3.
>
> So my questions are:
>
> 1) How can I fix this problem and make sure it never happens again?
>
> 2) In the short run how can I break slony out of its loop? Can I find
> this entry in sl_log_X somewhere and delete it?
If you can identify which row in sl_log_X contains the offending line
you could change the log_cmddata (with an UPDATE statement) to not have
the offending character (keep in mind this is the SQL that will kept
executed on your subscribers and you want the data on your subscribers
and master to be the same)
> _______________________________________________
> Slony1-general mailing list
> [email protected]
> http://lists.slony.info/mailman/listinfo/slony1-general
--
Steve Singer
Afilias Canada
Data Services Developer
416-673-1142
_______________________________________________
Slony1-general mailing list
[email protected]
http://lists.slony.info/mailman/listinfo/slony1-general
