X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 89CBD8B9F38 for ; Tue, 8 Feb 2005 15:35:42 +0000 (GMT) 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 24013-06 for ; Tue, 8 Feb 2005 15:35:29 +0000 (GMT) Received: from out010.verizon.net (out010pub.verizon.net [206.46.170.133]) by svr1.postgresql.org (Postfix) with ESMTP id 473968B9F07 for ; Tue, 8 Feb 2005 15:35:32 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by out010.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050208153532.YYQD25879.out010.verizon.net@jfradkin> for ; Tue, 8 Feb 2005 09:35:32 -0600 From: "Joel Fradkin" To: Subject: Did a good restore Date: Tue, 8 Feb 2005 10:39:02 -0500 Message-ID: <004b01c50df4$51ab2880$797ba8c0@jfradkin> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_004C_01C50DCA.68D52080" X-Authentication-Info: Submitted using SMTP AUTH at out010.verizon.net from [66.15.127.235] at Tue, 8 Feb 2005 09:35:32 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.197 tagged_above=0 required=5 tests=AWL, HTML_MESSAGE, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200502/107 X-Sequence-Number: 20218 This is a multi-part message in MIME format. ------=_NextPart_000_004C_01C50DCA.68D52080 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I just wanted to thank those who helped me. I finally hit it on the head, was the SQL_ASCHII versus UNICODE. I am not sure why I got my original database in SQL_ASCHII, but when I did my create with it and restored to it it was fine. I am going to try my create with UNICODE (the default it seems unless from command line) and run my app to copy my data over to see if I can then backup and restore ok with UNICODE. I have the feeling I will be better off using it as we do anticipate foreign language users. Joel Fradkin ------=_NextPart_000_004C_01C50DCA.68D52080 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I just wanted to thank those who helped = me.

I finally hit it on the head, was the SQL_ASCHII = versus UNICODE.

I am not sure why I got my original database in = SQL_ASCHII, but when I did my create with it and restored to it it was = fine.

I am going to try my create with UNICODE (the default = it seems unless from command line) and run my app to copy my data over to = see if I can then backup and restore ok with UNICODE. I have the feeling I will = be better off using it as we do anticipate foreign language = users.

Joel Fradkin

------=_NextPart_000_004C_01C50DCA.68D52080--