Skip site navigation (1) Skip section navigation (2)

Re: pg_dumpall problems

From: "Peter Koczan" <pjkoczan(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: pg_dumpall problems
Date: 2007-01-31 18:23:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
On 1/30/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Peter Koczan" <pjkoczan(at)gmail(dot)com> 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

I misunderstood your question. I apologize. Granting access on "postgres"
worked like a charm. Thank you.


In response to

pgsql-admin by date

Next:From: Chris HooverDate: 2007-01-31 21:08:06
Subject: 8.1.3 Problem
Previous:From: airbulb Date: 2007-01-31 18:14:41
Subject: Unable to pg_dump 8.1.2 - memory alloc error

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group