Chris Curvey wrote: > My vendor took a dump of our "something else" database (which runs on Windows), did their conversion > to Postgres, and then sent me back a postgres dump (custom format) of the database for me to load onto > my servers for testing. > > > I was interested to find that while I can load the dump onto a PG 9.3 server running on Windows, I'm > unable to load it on either 9.2 or 9.3 running on Linux. At some point during the restore process > (and it's not a consistent point), PG on Linux crashes. You mean, the database server dies? Or that there is an error message? If it is the latter, can we see the error message? > I suspect that the problem is related to the encoding specified in the database dump: > > CREATE DATABASE "TestDatabase" WITH TEMPLATE = template0 ENCODING = 'UTF8' LC_COLLATE = > 'English_United States.1252' LC_CTYPE = 'English_United States.1252'; Yes, that should throw an error on a Linux system. But you should get that error consistently, different from what you write above. > So my questions for the brain trust are: > > > 1) Would you expect this to work? No, as stated above. > 2) If I had to load this database on Linux, what would be the best way to go about it? (see if I can > find that charset/encoding for Linux? Ask the vendor for a plain-text dump? ) You can create the database beforehand and ignore the one error from pg_restore. You can convert the custom format dump into an SQL file with pg_restore -f dumpfile.sql dumpfile.dmp Yours, Laurenz Albe -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
