Fri Jan 12 09:12:04 PST 2007
- Previous message: [Slony1-general] Initial copy fails - corrupt source table?
- Next message: [Slony1-general] SLONY-I disadvantages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Jan 12, 2007 at 08:24:02AM -0700, Dave Price wrote: > Well, I see a problem ... db4 is my slave target, db2 is the live > database, db3 is the master I am using to test with first - restored > backup from db2 ... > > db3 appears to be defaulting to UTF8 not SQL_ASCII like the other two servers. Your output suggested that db4 was the one with UTF-8. You have to specify this at database creation time. So you should drop the databases and recreate them with SQL_ASCII encoding. One thing to check is your locale on the machine; if that's UTF-8, UTF-8 is what you'll get in the database. A -- Andrew Sullivan | ajs at crankycanuck.ca Information security isn't a technological problem. It's an economics problem. --Bruce Schneier
- Previous message: [Slony1-general] Initial copy fails - corrupt source table?
- Next message: [Slony1-general] SLONY-I disadvantages
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list