Wed Mar 12 10:03:28 PDT 2008
- Previous message: [Slony1-general] UTF-8 encoding Error
- Next message: [Slony1-general] Slave upgrade without break replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 2008-03-12 at 02:30 -0700, ajcity wrote: > Hi all, > I'm replicating a database that has 8 tables. 7 of them replicate fine on > first replication but the last table (reports table) keeps giving this error > whenever I try to replicate it: > 2008-03-07 08:59:31 EST ERROR remoteWorkerThread_1: copy from stdin on > local node - PGRES_FATAL_ERROR ERROR: invalid byte sequence for encoding > "UTF8": 0x80 > > 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". > I have ran a SET CLIENT_ENCODING TO 'UTF-8' command on both the master and > slave databases and I keep getting the same error. SET commands are only active for that session. > I have also dropped the > table on the slave and recreated it with the exact schema of the master and > still the same error. > I noticed that if I use pg_dump to extract the data on the reports table of > the master and I insert it into the table on the slave, I don't get that > error. Also, it seems to be giving the error on the last row of the table > and the table is dynamically updated (on the average 5 times within the > hour). Before I read this paragraph, I thought maybe you got some invalid byte sequences in your data, which is possible before 8.3. If you can dump/reload fine, that's probably not the case. What versions are the two servers? Do they both have the same encoding and locale settings? Regards, Jeff Davis
- Previous message: [Slony1-general] UTF-8 encoding Error
- Next message: [Slony1-general] Slave upgrade without break replication
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list