Received: from sss.pgh.pa.us ([192.204.191.242])
	by postgresql.org (8.11.3/8.11.4) with ESMTP id g16GXRE81435
	for <pgsql-admin@postgresql.org>; Wed, 6 Feb 2002 11:33:27 -0500 (EST)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g16GXUf06702;
	Wed, 6 Feb 2002 11:33:30 -0500 (EST)
To: s.chava@wcom.com (Srinivasa Rao Chava)
cc: pgsql-admin@postgresql.org
Subject: Re: pg_restore 
In-reply-to: <66d229f1.0202060747.39b66049@posting.google.com> 
References: <66d229f1.0202060747.39b66049@posting.google.com>
Comments: In-reply-to s.chava@wcom.com (Srinivasa Rao Chava)
	message dated "06 Feb 2002 07:47:38 -0800"
Date: Wed, 06 Feb 2002 11:33:30 -0500
Message-ID: <6699.1013013210@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Archive-Number: 200202/44
X-Sequence-Number: 3205

s.chava@wcom.com (Srinivasa Rao Chava) writes:
> Archiver(db): Could not execute query. Code = 7. Explanation from
> backend: 'ERROR:  mysequence.setval: you don't have permissions to set
> sequence mysequence

Hmm, I think I see an oversight in pg_dump.  Exactly what options did
you give to pg_dump and pg_restore?

			regards, tom lane