From: | Pavel Luzanov <p(dot)luzanov(at)postgrespro(dot)ru> |
---|---|
To: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Things I don't like about \du's "Attributes" column |
Date: | 2023-12-31 10:52:28 |
Message-ID: | 6fbfb5ce-5613-43bf-8a84-3da1c0da4746@postgrespro.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30.12.2023 17:33, Isaac Morland wrote:
> Would it make sense to make the column non-nullable and always set it
> to infinity when there is no expiry?
A password is not required for roles. In many cases, external
authentication is used in ph_hba.conf.
I think it would be strange to have 'infinity' for roles without a password.
Tom suggested to have 'infinity' in the \du output for roles with a
password.
My doubt is that this will hide the real values (absence of values). So
I suggested a separate column
'Has password?' to show roles with password and unmodified column
'Password expire time'.
Yes, it's easy to replace NULL with "infinity" for roles with a
password, but why?
What is the reason for this action? Absence of value for 'expire time'
clear indicates that there is no time limit.
Also I don't see a practical reasons to execute next command, since it
do nothing:
ALTER ROLE .. PASSWORD 'infinity';
So I think that in most cases there is no "infinity" in the
rolvaliduntil column.
But of course, I can be wrong.
Thank you for giving your opinion.
--
Pavel Luzanov
Postgres Professional:https://postgrespro.com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2023-12-31 11:00:04 | Re: pg_stat_statements: more test coverage |
Previous Message | Kyotaro Horiguchi | 2023-12-31 09:36:34 | Re: A typo in a messsage? |