On Wed, Dec 7, 2016 at 8:33 AM, Michael Sheaver <msheaver@me.com> wrote:
with this for a couple days about a year ago, the workaround I found that works is to first import it into a MySQL table, strip out the characters in MySQL, dump the data out to a CSV and finally bring the sanitized data into Postgres using the copy command.
Couldn't you load them into an SQL_ASCII postgres database and accomplish the same?
I have a utility I wrote to migrate our entire production DB from SQL_ASCII to UTF8. It works *really* well, and introspects your database to figure out what to do, one table at a time. You'd avoid the need for CSV importing. Just dump/reload into UTF8 database and be done.
