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 9F7BE8B9F19 for ; Thu, 3 Feb 2005 19:55:12 +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 82725-03 for ; Thu, 3 Feb 2005 19:55:07 +0000 (GMT) Received: from out006.verizon.net (out006pub.verizon.net [206.46.170.106]) by svr1.postgresql.org (Postfix) with ESMTP id 96DDD8B9F11 for ; Thu, 3 Feb 2005 19:55:07 +0000 (GMT) Received: from jfradkin ([66.15.127.235]) by out006.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050203195506.CDGX28674.out006.verizon.net@jfradkin>; Thu, 3 Feb 2005 13:55:06 -0600 From: "Joel Fradkin" To: "'Tom Lane'" , "'Richard Huxton'" Cc: Subject: Re: problem with backup and restore (probaly stupit newb thing) Date: Thu, 3 Feb 2005 14:58:29 -0500 Message-ID: <000001c50a2a$bc552cd0$797ba8c0@jfradkin> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable In-Reply-To: <17474.1107454601@sss.pgh.pa.us> X-Authentication-Info: Submitted using SMTP AUTH at out006.verizon.net from [66.15.127.235] at Thu, 3 Feb 2005 13:55:06 -0600 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=3.178 tagged_above=0 required=5 tests=AWL, MSGID_DOLLARS X-Spam-Level: *** X-Archive-Number: 200502/75 X-Sequence-Number: 20186 I am not running version 8 (I did try this on the linux box as well, but = the version I documented was the server is linux and the client is XP). I ran it from PG admin in both cases, maybe I need to just run from the command line on the linux box (this is fine as long as I can backup the = file and restore it if need be). I did the dump and restore from the = PGadminIII program so maybe the data base is not (UTF-8). I am new to this so I do = not know how to determine and set the types so they match up. I did a create database and am running a .net app to read the data from MSSQL and add it to Postgres. If anyone know a quick to determine this and what the syntax mods are = for the dump and restore I would be very happy, if not I can play around. = Thanks so much for all the help, maybe I should load version 8 (I was not sure there were rpms for fedora 3 that worked, I tried to load it and was obviously not doing it correctly). Joel Fradkin =20 Wazagua, Inc. 2520 Trailmate Dr Sarasota, Florida 34243 Tel. 941-753-7111 ext 305 =20 jfradkin@wazagua.com www.wazagua.com Powered by Wazagua Providing you with the latest Web-based technology & advanced tools. C 2004. WAZAGUA, Inc. All rights reserved. WAZAGUA, Inc This email message is for the use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized = review, use, disclosure or distribution is prohibited. If you are not the = intended recipient, please contact the sender by reply email and delete and = destroy all copies of the original message, including attachments. =20 =20 -----Original Message----- From: Tom Lane [mailto:tgl@sss.pgh.pa.us]=20 Sent: Thursday, February 03, 2005 1:17 PM To: Richard Huxton Cc: Joel Fradkin; pgsql-sql@postgresql.org Subject: Re: [SQL] problem with backup and restore (probaly stupit newb thing)=20 Richard Huxton writes: > Joel Fradkin wrote: >> ServerVersion: 07.03.0200 PostgreSQL 7.4.6 on i386-redhat-linux-gnu, >> compiled by GCC i386-redhat-linux-gcc (GCC) 3.4.2 20041017 (Red Hat = 3.4.2 > OK - let's start here. The syntax here is fine, I just tested it on an = > 8.0 database. Are you sure the DB you are restoring to is version 8? Looks to me like he's trying to use 8.0 pg_dump/pg_restore to reload into a 7.4 server. This definitely won't work without specifying --disable-dollar-quoting to pg_dump; and if you care about restoring object ownership correctly, also --use-set-session-authorization. I don't recall if there are any other gotchas. The unicode issue I'm not sure about. Perhaps the original database was SQL_ASCII encoding and so was allowed to contain byte sequences that aren't legal unicode? regards, tom lane