On Tuesday, February 08, 2011 2:44:51 pm Mike Christensen wrote: > >> 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. Two possibilities, it is being run as the RubyMine user or as the user that is specified in the connection information RubyMine is using to pull and push data to the database. -- Adrian Klaver adrian.klaver@xxxxxxxxx -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
