X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8140D535BE; Thu, 12 May 2005 18:58:14 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 98313-08; Thu, 12 May 2005 21:58:04 +0000 (GMT) Received: from fep07-app.kolumbus.fi (fep07-0.kolumbus.fi [193.229.0.51]) by svr1.postgresql.org (Postfix) with ESMTP id C9C4D53472; Thu, 12 May 2005 18:58:02 -0300 (ADT) Received: from [80.186.194.169] by fep07-app.kolumbus.fi with ESMTP id <20050512215804.QFFH9540.fep07-app.kolumbus.fi@[80.186.194.169]>; Fri, 13 May 2005 00:58:04 +0300 Message-ID: <4283D16B.80408@kolumbus.fi> Date: Fri, 13 May 2005 00:58:03 +0300 From: Marko Ristola User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050420 Debian/1.7.7-2 X-Accept-Language: en MIME-Version: 1.0 To: Joel Fradkin Cc: 'Bricklen Anderson' , pgsql-odbc@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [ODBC] catastrophic error References: <002401c55733$a922b5a0$797ba8c0@jfradkin> In-Reply-To: <002401c55733$a922b5a0$797ba8c0@jfradkin> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.315 tagged_above=0 required=5 tests=AWL, DNS_FROM_RFC_ABUSE, FORGED_RCVD_HELO X-Spam-Level: X-Archive-Number: 200505/175 X-Sequence-Number: 17604 About ASCII to Unicode conversion (if you have only Latin1 characters in the database): Here is a receipt, how you can do a charset conversion from SQL_ASCII into UNICODE on the Linux side: (check these from manual pages first!): 1. Stop PostgreSQL and make a good backup! "su - postgres" ; "pg_dumpall -D > everything-latin1.dump" "file everything-latin1.dump" might tell you the charset. Watch out for \345 style octal numbers, because iconv character converter won't see them. PostgreSQL protects non-ascii characters that way at least in ASCII backups. (The -D above makes the restore phase slow. I use it if I switch a PostgreSQL version, because the rows are standard SQL sentences. Very portable. The slowness can be resolved at least by filtering the file with AWK and combining many inserts into a single transaction (BEGIN,many inserts, COMMIT). ) cat everything-latin1.dump | iconv -f LATIN1 -t UTF-8 > everything-utf8.dump stop PostgreSQL. remove the old database Check PostgreSQL configuration files! su - postgres initdb with UTF-8. su - postgres ; psql -f everything-utf8.dump template1 Please check the above phases, but that is approximately, how it goes. Additional documentation: man pg_dumpall, man initdb, man createdb, man psql, man iconv Database speed: speed loader format is fastest on restore (pg_dumpall without -D). Inserts within reasonable sized transactions are lots of faster than inserts in autocommit mode (pg_dumpall with -D). Good night. Marko Ristola Joel Fradkin wrote: >The catastrophic error was the actual text sent from the IIS component >error. > >SO I am not 100% sure what it means, I believe it is just mirroring back >text from the dbserver when trying to connect and failing. > >I am guessing it is odbc and I am currently using the 7.4 version, but am >looking for the best way to move from SQL_ASCHII to UNICODE (maybe a backup >and restore using some kind of params? I hope? > >If not I guess I could alter my original program that read MSSQL to read >from postgres and write it back to a Unicode database and see if the odbc >drivers are ok (it originally blew up and that's how I ended up using >SQL_ASCHII). > >Joel Fradkin > >What does a catastrophic error consist of? Do you mean your IIS servers >could no longer connect to the db, and yet you _could_ connect to the db via >pgadmin? Yes the web interface gave that as the conection error string (my >error routine just prints that to the screen) >I would have thought that rebooting the IIS would have solved any >connectivity issues (assuming that that is the error that you are getting). >I've never used IIS, so I can't even guess about that. ODBC is a >possibility, I suppose, and it certainly wouldn't hurt to try again on the >ODBC list. > > >Cheers, > >Bricklen > > >