Re: Permission denied error - best way to fix?
От | Mike Christensen |
---|---|
Тема | Re: Permission denied error - best way to fix? |
Дата | |
Msg-id | AANLkTi=Tj1_5ai167hkL-no8JAcg04NY53+fZrp7X+=i@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Permission denied error - best way to fix? (Adrian Klaver <adrian.klaver@gmail.com>) |
Ответы |
Re: Permission denied error - best way to fix?
Re: Permission denied error - best way to fix? |
Список | 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.
В списке pgsql-general по дате отправления: