Steve Burrows <[EMAIL PROTECTED]> writes: > Csaba, > Thanks, very helpful. I have removed the foreign keys from my replica schema. > All - as regards the UTF-8 problem, I am replicating from a DB which is > SQL-ASCII to a db which is UTF-8. I want to do > this, while my initial purpose is backup it will become, in due course, an > upgrade, and I want the upgraded version to be > unicode. Is this possible - are there any configuration options I need to set > in postgres / slony to enable it - it seems > at the moment that I may not be able to do an upgrade to PostgreSQL 8.1 via > Slony - I may be forced down the dump/restore > route in order to correct the encoding in the dump file?
There surely should be some better way, such as finding which specific tuples are problematic, and updating them on the source database. A thought... You might do two dumps: 1. Raw, no conversion using iconv 2. Another, which converts using iconv [generate this by passing file #1 thru iconv...] Diffing those files should give you a pretty clear idea which records are troublesome. -- (format nil "[EMAIL PROTECTED]" "cbbrowne" "ca.afilias.info") <http://dba2.int.libertyrms.com/> Christopher Browne (416) 673-4124 (land) _______________________________________________ Slony1-general mailing list [email protected] http://gborg.postgresql.org/mailman/listinfo/slony1-general
