| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(at)enterprisedb(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: rolcanlogin vs. the flat password file |
| Date: | 2007-10-17 16:09:25 |
| Message-ID: | 471633B5.3090301@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
/D
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2007-10-17 16:33:22 | Re: Why copy_relation_data only use wal whenWALarchiving is enabled |
| Previous Message | Stephen Frost | 2007-10-17 15:35:41 | Re: rolcanlogin vs. the flat password file |