Received: from localhost (maia-4.hub.org [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 85F769FB42E for ; Tue, 30 Jan 2007 20:26:44 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-new, port 10024) with ESMTP id 09701-10 for ; Tue, 30 Jan 2007 20:26:27 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id E90939F9F8D for ; Tue, 30 Jan 2007 20:26:26 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id l0V0QOI7013725; Tue, 30 Jan 2007 19:26:25 -0500 (EST) To: "Peter Koczan" cc: pgsql-admin Subject: Re: pg_dumpall problems In-reply-to: <4544e0330701301534r5cb09722i5665f2f406dd29fc@mail.gmail.com> References: <4544e0330701291303u2ed1d2bclff520f6ecc99e832@mail.gmail.com> <20835.1170110152@sss.pgh.pa.us> <4544e0330701301534r5cb09722i5665f2f406dd29fc@mail.gmail.com> Comments: In-reply-to "Peter Koczan" message dated "Tue, 30 Jan 2007 17:34:07 -0600" Date: Tue, 30 Jan 2007 19:26:24 -0500 Message-ID: <13724.1170203184@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200701/284 X-Sequence-Number: 24440 "Peter Koczan" writes: > So, is there any remedy to my problem (see below) short of granting > superuser access? Is this a bug (which I would then report on the > appropriate channels)? It's not a bug. > As for Tom's suggestion, there's no way to specify the database in > pg_dumpall, only the server, and the same bug occurs if I run as the user on > the same server and cluster with the same major version. You still haven't responded to my query: did you try it in the same database that pg_dumpall is connecting to? My guess is that you have munged the permissions on pg_shadow or pg_authid without understanding that that will only take effect in the one database you do it in. pg_dumpall is connecting to either "postgres" or "template1" depending on version; what's the permissions situation in that database? regards, tom lane