Received: from maia.hub.org (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 6F5736338FE for ; Tue, 23 Feb 2010 05:36:24 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 79215-08 for ; Tue, 23 Feb 2010 09:36:08 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-bw0-f216.google.com (mail-bw0-f216.google.com [209.85.218.216]) by mail.postgresql.org (Postfix) with ESMTP id 1347D63291D for ; Tue, 23 Feb 2010 05:36:12 -0400 (AST) Received: by bwz8 with SMTP id 8so2525814bwz.3 for ; Tue, 23 Feb 2010 01:36:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=rJTtXCueovksAEb6pJXVKHjwpZ4gr9MY4D4K8h02p64=; b=Ei/SpeRjNmq51mCoEo7GeqzEyWejfmXdksFr1cJqjz/PlC8HimxBHHcEFz2R4WT9HH QbxCjnS4CW1UAhDGmK8/6PxksysOK/2N13EABGZwIe5qQ7dCl19j2cnT0W53s/3QHOxW Sk5kqC21PHe1r+nAZcoRnbUQ0ivnzo7YHSn2I= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=aeWfAV9uS+/h5606tWxtCmYZmIn5MHdZ/wXU8ugpgDa8C6rYqKu7PWnbxszfzuX2KF tM4yJfLlqWDEnqMcg3B34hbeHpzOMcqDDqP+IAjOx0pzO1cymoQVy2g7xY4CPOtGFcPQ p/R/E/53A/kYjDTABFsdSLU9LusQThA+MMZXQ= MIME-Version: 1.0 Received: by 10.204.6.203 with SMTP id a11mr1296665bka.33.1266917771166; Tue, 23 Feb 2010 01:36:11 -0800 (PST) In-Reply-To: References: <4B830D12020000250002F4C1@gw.wicourts.gov> From: Ian Lea Date: Tue, 23 Feb 2010 09:35:51 +0000 Message-ID: <8c4e68611002230135x22f9f855ocd777d9d9545d594@mail.gmail.com> Subject: Re: how do I do dump and restore without bugging with constraint? To: pgsql-admin@postgresql.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.413 tagged_above=-10 required=5 tests=AWL=0.186, BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201002/173 X-Sequence-Number: 33776 It is unreasonable to expect 8.3 programs to be able to understand everything that 8.4 programs might write. What format is your dump in? Plain text (--format=3Dp) might work. Or try dumping the 8.4 database with the 8.3 version of pg_dump, or maybe use the 8.4 pg_restore against the 8.3 database. -- Ian. On Tue, Feb 23, 2010 at 9:17 AM, Net Tree Inc. wrote= : > Why am I keep getting error with version issues.... I am trying to restor= e a > backup file from a 8.4 postgresql server to a 8.3 postgresql server. > [postgres@localhost ~]$ pg_restore -C -d postgres -i isamdb.backup > pg_restore.bin: [archiver] unsupported version (1.11) in file header > > On Tue, Feb 23, 2010 at 1:02 PM, Kevin Grittner > wrote: >> >> "Net Tree Inc." =A0wrote: >> >> > When I do restore it shown alot errors related with constraints. >> > How can I dump and to restore from old to new without dealing with >> > constraint and just forces data dump to where it suppose to belong? >> >> What version are you dumping from and to? =A0Exactly what errors are >> you getting? =A0(Copy and paste samples, please.) >> >> You might want to review this page: >> >> http://wiki.postgresql.org/wiki/Guide_to_reporting_problems >> >> -Kevin >> >> > > > > -- > --------------------------------------- > Steven Huang >