X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 731779DC818 for ; Fri, 10 Feb 2006 04:38:32 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 26112-09 for ; Fri, 10 Feb 2006 04:38:32 -0400 (AST) Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159]) by postgresql.org (Postfix) with ESMTP id CEE449DC81A for ; Fri, 10 Feb 2006 04:38:29 -0400 (AST) Received: from ctb-mesg8.saix.net (ctb-mesg8.saix.net [196.25.240.78]) by svr4.postgresql.org (Postfix) with ESMTP id 511E25AF0D0 for ; Fri, 10 Feb 2006 08:38:31 +0000 (GMT) Received: from mygus (dsl-146-121-181.telkomadsl.co.za [165.146.121.181]) by ctb-mesg8.saix.net (Postfix) with ESMTP id 0654A4480 for ; Fri, 10 Feb 2006 10:38:24 +0200 (SAST) From: "James Dey" To: Subject: Migration Date: Fri, 10 Feb 2006 10:38:23 +0200 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_003D_01C62E2E.1F74A7F0" X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcYuHVpT4zM5ZM78S96AAlq7h1OO3g== Message-Id: <20060210083824.0654A4480@ctb-mesg8.saix.net> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.121 required=5 tests=[AWL=0.120, HTML_MESSAGE=0.001] X-Spam-Score: 0.121 X-Spam-Level: X-Archive-Number: 200602/95 X-Sequence-Number: 20516 This is a multi-part message in MIME format. ------=_NextPart_000_003D_01C62E2E.1F74A7F0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi Everyone, I'm a newbie to the list, and look forward to helping out where I can if possible. I have an issue which I've not been able to get around. I have a Postgresql 7.4 server with a number of databases: Name | Owner | Encoding ------------+----------+---------- xxx45 | postgres | UNICODE xxx30 | postgres | UNICODE xxx30_copy | postgres | UNICODE yyy30 | postgres | UNICODE xxxxxxx | postgres | UNICODE xxxx | postgres | UNICODE I have installed PostgreSQL 8.1 onto a new box, and when trying to create a new database, even when specifiying -encoding=UNICODE I cannot create UNICODE dbs, it makes them all UTF-8. Then when I try and restore a DB dump, but keep on getting invalid "UTF-8 byte sequence detected near byte xxx" and although the restore continues, a lot of data is missing. Does anyone have any suggestions here, I would really appreciate it! Regards, James Dey tel +27 11 704-1945 cell +27 82 785-5102 fax +27 11 388-8907 mail james@mygus.com myGUS / SLT retains all its intellectual property rights in any information contained in e-mail messages (or any attachments thereto) which relates to the official business of myGUS / SLT or of any of its associates. Such information may be legally privileged, is to be treated as confidential and myGUS / SLT will take legal steps against any unauthorised use. myGUS / SLT does not take any responsibility for, or endorses any information which does not relate to its official business, including personal mail and/or opinions by senders who may or may not be employed by myGUS / SLT. In the event that you receive a message not intended for you, we request that you notify the sender immediately, do not read, disclose or use the content in any way whatsoever and destroy/delete the message immediately. While myGUS / SLT will take reasonable precautions, it cannot ensure that this e-mail will be free of errors, viruses, interception or interference therewith. myGUS / SLT does not, therefore, issue any guarantees or warranties in this regard and cannot be held liable for any loss or damages incurred by the recipient which have been caused by any of the above-mentioned factors. ------=_NextPart_000_003D_01C62E2E.1F74A7F0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi Everyone,

 

I’m a newbie to the list, and look forward to = helping out where I can if possible.

 

I have an issue which I’ve not been able to get around. I have a Postgresql 7.4 server with a number of = databases:

    Name    |  Owner   | Encoding

------------+----------+----------

 xxx45      | postgres = | UNICODE

 xxx30      | postgres = | UNICODE

 xxx30_copy | postgres | = UNICODE

 yyy30      | postgres = | UNICODE

 xxxxxxx  | postgres | = UNICODE

 xxxx     | postgres | = UNICODE

 

I have installed PostgreSQL 8.1 onto a new box, and = when trying to create a new database, even when specifiying = –encoding=3DUNICODE I cannot create UNICODE dbs, it makes them all = UTF-8.


Then when I try and restore a DB dump, but keep on getting = invalid “UTF-8 byte = sequence detected near byte xxx” and although the restore continues, a lot = of data is missing.

 

Does = anyone have any suggestions here, I would really appreciate = it!


Regards,

 

James = Dey

 =

t= el           = +27 11 = 704-1945

c= ell       &= nbsp;  +27 82 785-5102

f= ax       &= nbsp;   +27 11 388-8907

m= ail        james@mygus.com<= /font>

 <= /span>

myGUS / SLT retains all its = intellectual property rights in any information contained in e-mail messages (or any attachments thereto) which relates to the official business of myGUS / = SLT or of any of its associates. Such information may be legally privileged, is = to be treated as confidential and myGUS / SLT will take legal steps against = any unauthorised use. myGUS / SLT does not take any responsibility for, or = endorses any information which does not relate to its official business, = including personal mail and/or opinions by senders who may or may not be employed = by myGUS / SLT. In the event that you receive a message not intended for = you, we request that you notify the sender immediately, do not read, disclose or = use the content in any way whatsoever and destroy/delete the message = immediately. While myGUS / SLT will take reasonable precautions, it cannot ensure = that this e-mail will be free of errors, viruses, interception or interference = therewith. myGUS / SLT does not, therefore, issue any guarantees or warranties in = this regard and cannot be held liable for any loss or damages incurred by the recipient which have been caused by any of the above-mentioned = factors.

 

------=_NextPart_000_003D_01C62E2E.1F74A7F0--