| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Rama Krishnan <raghuldrag(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Valid until |
| Date: | 2024-05-14 15:27:02 |
| Message-ID: | 7dff9a17-744d-437b-847c-18c161c8a901@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 5/14/24 00:57, Rama Krishnan wrote:
> Hi team,
>
> I have a question about the "valid until" parameter in the "create role"
> command.
>
> I recently set a user's password validity to "2024-05-13", but despite
> this, the user is still able to connect to the database. Is this a bug,
> or is the "valid until" parameter just for identification purposes,
> indicating when the password will expire?
>
> Could you please clarify this for me?
https://www.postgresql.org/docs/current/sql-createrole.html
"
VALID UNTIL 'timestamp'
The VALID UNTIL clause sets a date and time after which the role's
password is no longer valid. If this clause is omitted the password will
be valid for all time.
"
When did the user log in?
What is the TimeZone setting in the database?
>
>
> Thanks
>
> Ram
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-05-14 15:45:09 | Re: Valid until |
| Previous Message | Dimitrios Apostolou | 2024-05-14 12:55:26 | Re: SELECT DISTINCT chooses parallel seqscan instead of indexscan on huge table with 1000 partitions |