Received: from localhost (unknown [200.46.208.211]) by mail.postgresql.org (Postfix) with ESMTP id 09DFF632AAE; Mon, 23 Mar 2009 12:04:24 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.208.211]) (amavisd-maia, port 10024) with ESMTP id 31734-09; Mon, 23 Mar 2009 12:04:20 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qw-out-2122.google.com (qw-out-2122.google.com [74.125.92.27]) by mail.postgresql.org (Postfix) with ESMTP id 42896632988; Mon, 23 Mar 2009 12:04:17 -0300 (ADT) Received: by qw-out-2122.google.com with SMTP id 8so930402qwh.61 for ; Mon, 23 Mar 2009 08:04:15 -0700 (PDT) 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 :date:message-id:subject:from:to:cc:content-type; bh=kuD5ErTnmL4GYz7vy04A7dqRYvbQvjYNJOarUjO0uDY=; b=a08jcVbzN7ZAyUJcbXSrQv4lC8S8H8HuyEOoS4u4nwkkTgHLi1YaaY8BUpUtqKLhvv arUhfBaneku35zvlvuHiubDjTK5EDsVnknegHRbs64a0hadhXddoo5VMNCeKJsMiAG/M Egwupn/0DTc7brdjjAWzYQ/ZsUhOMax3cML0k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=iuZsA5zIvcuQaFT0gCDbHR4N5ASVXA2P8bGAa7GjPrebqagvKmZI+PrIp2GLrsSw7e lBcua7eL4OPHY4VIVIWgYgjd+f3OuhMJhvbfWckrMM0F4wC8+8NH/coJH8cnpShLcYTv ljDAs6GapTq9I/Z1ZqRx/Kku+QqkwmhgfaAhs= MIME-Version: 1.0 Received: by 10.143.3.4 with SMTP id f4mr2892011wfi.299.1237820654668; Mon, 23 Mar 2009 08:04:14 -0700 (PDT) In-Reply-To: <6A77C6F2-BD7E-47F3-85A4-BDF39C71FE6D@engineyard.com> References: <6A77C6F2-BD7E-47F3-85A4-BDF39C71FE6D@engineyard.com> Date: Mon, 23 Mar 2009 08:04:14 -0700 Message-ID: Subject: Re: pg_restore error - Any Idea? From: DM To: Erik Jones Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org Content-Type: multipart/alternative; boundary=001636e90cd86acdc20465ca94cc X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200903/988 X-Sequence-Number: 145574 --001636e90cd86acdc20465ca94cc Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Eric, There was no change in the version, we are using postgres v8.3.5 Thanks Deepak On Sun, Mar 22, 2009 at 11:17 PM, Erik Jones wrote: > > On Mar 22, 2009, at 10:44 PM, DM wrote: > > Hi All, >> >> I am facing an error on executing the below command >> >> dump name: pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing >> databae name: pnqd_test >> >> $pg_restore -U postgres -p 5433 -d pnqd_test >> pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing >> >> pg_restore: [archiver (db)] Error while PROCESSING TOC: >> pg_restore: [archiver (db)] Error from TOC entry 3715; 0 0 ACL monitor >> postgres >> WARNING: errors ignored on restore: 1 >> >> I am not able to figure out this issue. Any idea guys. >> > > > TOC -> Table of Contents > > A dump made with pg_dump's -Fc will contain a table of contents of all of > the database objects in the dump file. Something in that is causing an > error for pg_restore. Does the version of pg_restore match up with the > version of pg_dump that you used to make the dump? > > Erik Jones, Database Administrator > Engine Yard > Support, Scalability, Reliability > 866.518.9273 x 260 > Location: US/Pacific > IRC: mage2k > > > > > > --001636e90cd86acdc20465ca94cc Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Eric,

There was no change in the version, we are using pos= tgres v8.3.5

Thanks
Deepak=A0

On Sun, Mar 22, 2009 at 11:17 PM, Erik Jones= <ejones@engi= neyard.com> wrote:

On Mar 22, 2009, at 10:44 PM, DM wrote:

Hi All,

I am facing an error on executing the below command

dump name: pg_dump_FcZ0.pnps_200903041201_1.2.1.0_base_testing
databae name: pnqd_test

$pg_restore -U postgres -p 5433 -d pnqd_test pg_dump_FcZ0.pnps_200903041201= _1.2.1.0_base_testing

pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 3715; 0 0 ACL monitor post= gres
WARNING: errors ignored on restore: 1

I am not able to figure out this issue. Any idea guys.


TOC -> Table of Contents

A dump made with pg_dump's -Fc will contain a table of contents of all = of the database objects in the dump file. =A0Something in that is causing a= n error for pg_restore. =A0Does the version of pg_restore match up with the= version of pg_dump that you used to make the dump?

Erik Jones, Database Administrator
Engine Yard
Support, Scalability, Reliability
866.518.9273 x 260
Location: US/Pacific
IRC: mage2k






--001636e90cd86acdc20465ca94cc--