From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
Cc: | vrms <vrms(at)netcologne(dot)de>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Guidance on user deletion |
Date: | 2024-05-12 13:41:38 |
Message-ID: | CAKFQuwbzfRCo3FhAK+ae51gV65N5judL7x7TnURY4UZo9r23Jg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Sunday, May 12, 2024, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
> On Sun, May 12, 2024 at 6:56 AM vrms <vrms(at)netcologne(dot)de> wrote:
>
>>
>> The five account systems I've had experience with (OpenVMS, Linux, Active
>> Directory, SQL Server, Postgresql) all have the ability to expire users,
>> and to unexpire them if the person ever returns.
>>
>> how do you practically expire an account in postgres?
>>
>
> ALTER ROLE ... VALID UNTIL 'timestamp';
>
>
I suppose, but that only expires the password, not invalidates the role.
There isn’t a concept of “invalid role”. If you want to prevent a role
from being used to login remove the login attribute.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Edwin UY | 2024-05-12 17:37:08 | ora2pg partitioned table DDL 'not working' |
Previous Message | Wasim Devale | 2024-05-12 13:33:03 | Postgis |