From: | Mike Christensen <mike(at)kitchenpc(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Permission denied error - best way to fix? |
Date: | 2011-02-08 22:44:51 |
Message-ID: | AANLkTi=Tj1_5ai167hkL-no8JAcg04NY53+fZrp7X+=i@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>> Here's the error:
>>
>> pg_dump: SQL command failed
>> pg_dump: Error message from server: ERROR: permission denied for
>> relation pantryitems
>> pg_dump: The command was: LOCK TABLE public.pantryitems IN ACCESS SHARE
>> MODE
>>
>> Does the user need to be a superuser, or is there some way to GRANT
>> this permission (if possible, I don't want this user to be able to
>> modify the schema)..
>>
>> Mike
>>
>
> pg_dump is an admin function so it will need to run as a role that can touch
> all requested objects and take action. For this particular case you could
> GRANT SELECT on that table to the restricted user. The trouble being is that
> this turns into a game of Whack-a-Mole fairly quickly. This is one of those
> situations where taken a long view on your permissions scheme will pay
> dividends.
Hmm interesting, I wonder if this error is happening because pg_dump
is being run from another program (RubyMine) and the process doesn't
have whatever access it needs.
From | Date | Subject | |
---|---|---|---|
Next Message | Ogden | 2011-02-08 22:46:51 | PostgreSQL 9.0 Streaming Replication Configuration |
Previous Message | Carlos Mennens | 2011-02-08 22:36:30 | No Password Access |