On 6 June 2012 14:12, Adrian Klaver <adrian.klaver@xxxxxxxxx> wrote: > SQL_ASCII is not an encoding, it is basically a way of saying encoding > ignored. Given that, outside knowledge of the encoding used for data > inserted into the database is needed to make the conversion to UTF8. In > other words do you have any idea of what encoding was used by the clients > that supplied data to the database? You're going to have to manage this process carefully. I believe the best tool for the job is pgloader: http://pgfoundry.org/projects/pgloader/ It's certainly not inconceivable that this sort of tool could automagically deduce encoding (albeit often inconclusively) in much the same manor as modern web browsers attempt to when they have no alternative. I don't see much demand for that though. -- Peter Geoghegan http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training and Services -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
