Re: One Role, Two Passwords

From: Stephen Frost <sfrost(at)snowman(dot)net>
To: Daniel Farina <drfarina(at)acm(dot)org>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: One Role, Two Passwords
Date: 2011-01-21 02:19:37
Message-ID: 20110121021937.GS30352@tamriel.snowman.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Daniel Farina (drfarina(at)acm(dot)org) wrote:
> On Thu, Jan 20, 2011 at 6:12 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > I'm not likely to write a patch for it, but if someone else writes one
> > I would be willing to (a) support it and (b) subject to consensus,
> > commit it.
>
> Wouldn't this require a client application to issue the GUC setting?
> Or could I somehow tell a role "You create objects as this user, and
> you cannot change this."

Errr, well, ok, this is curious.

gis=> alter user sfrost set role gis;
ALTER ROLE
gis=> ^D\q
beren:/home/sfrost> psql --cluster 8.4/main -d gis
psql (8.4.5)
Type "help" for help.

gis=> show role;
role
------
gis
(1 row)

I'm trying to figure out if that'd help you or not, but it might. The
problem is that you'd have to change both the login userid and the
password, but you could make everything both those login roles do be
'as' some third role that's the 'real' role for the user.

I'm still looking for 'default owner for schema', but I guess that's
just me.

Thanks,

Stephen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-01-21 02:24:44 Re: REVIEW: EXPLAIN and nfiltered
Previous Message Kevin Grittner 2011-01-21 02:17:42 Re: REVIEW: EXPLAIN and nfiltered