| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Peter Koczan" <pjkoczan(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: pg_dumpall problems |
| Date: | 2007-01-31 00:26:24 |
| Message-ID: | 13724.1170203184@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Kinsella | 2007-01-31 01:27:21 | Cannot initdb for 8.2.1 - "..../postgres.bki" does not exist |
| Previous Message | Peter Koczan | 2007-01-30 23:34:07 | Re: pg_dumpall problems |