From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: rolcanlogin vs. the flat password file |
Date: | 2007-10-17 16:39:12 |
Message-ID: | 20071017163912.GE6268@svr2.hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 17, 2007 at 05:09:25PM +0100, Dave Page wrote:
> Stephen Frost wrote:
> > * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> >> Heikki Linnakangas <heikki(at)enterprisedb(dot)com> writes:
> >>> There's legitimate use for creating a role with NOLOGIN and a password.
> >> If we think that, then we shouldn't have a message at all.
> >
> > I'm not sure I agree with that. I don't agree that there's really a
> > legitimate use for creating a role w/ NOLOGIN and a password either, for
> > that matter.
>
> Preparing a new user account prior to an employee starting? In my last
> post we would do that regularly - setup all the accounts etc for the new
> user, but disable them all until the start date.
Yeah, but did you actually set a password for them?
We do that all the time here, but we don't set the passwords until they
show up.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2007-10-17 16:41:00 | Re: rolcanlogin vs. the flat password file |
Previous Message | Heikki Linnakangas | 2007-10-17 16:36:48 | Re: Why copy_relation_data only use wal whenWALarchivingis enabled |