Thu Apr 29 11:59:17 PDT 2010
- Previous message: [Slony1-general] encoding problems
- Next message: [Slony1-general] encoding problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jan Wieck wrote: > On 4/27/2010 7:22 PM, jks at selectacast.net 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". >> >> 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. > > You mean the DB encodings are both UTF8? Yes > > First thing to check then is if the client_encoding, used by the slon > process on both databases the same? You can set that explicitly for the > slon DB user with ALTER USER; > pg_user shows nothing in useconfig, so that means the system default (utf8) should be used, right? Anyway I set the client_encoding and it didn't help. I wish that error message in postgres was a little more descriptive and said what the client_encoding was.
- Previous message: [Slony1-general] encoding problems
- Next message: [Slony1-general] encoding problems
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list