Subject: pg_dump roles support
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 12/10/2007 11:19:55 AM
Stephen Frost <sfrost@snowman.net> writes:
> create role admin with noinherit;
> grant postgres to admin;
> grant admin to joesysadmin;
> pg_dump -U joesysadmin mydb;
> Fails because joesysadmin hasn't got rights to everything directly.
Seems like the correct answer to that is "use a saner role
configuration".
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
Subject: pg_dump roles support
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 12/10/2007 11:27:55 AM
Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> Seems like the correct answer to that is "use a saner role
>> configuration".
> Far as I can tell anyway. What would you suggest? The point here is
> that joesysadmin shouldn't get full postgres privs on login since most
> of the time he won't need them.
It's sane to set up a manually-used admin account that way, I agree.
What doesn't follow is that an account configured for manual use should
be used for non-interactive stuff like pg_dump.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|