On 04.02.26 18:44, Zsolt Parragi wrote:
>>> Alternatively, just print the actual expiration timestamp.
>>
>> That crossed my mind, but I worried about timezone/formatting questions,
>> and I haven't found any examples of putting a timestamp in an error message
>> like this. Is it acceptable to use pg_strftime() in a translated string?
>
> Wouldn't that be more confusing?
>
> The password for role "foo" will expire at 2026-02-05 16:56"
>
> No matter which date format is used, this is harder to understand than
>
> The password for role "foo" will expire in 1 day(s)
>
> or
>
> The password for role "foo" will expire in 22 hour(s) 16 minute(s)
>
> All 3 are about a password expiring around the same time plus minus a
> few hours, but the first one is significantly harder to figure out,
> first I have to think about what's the exact date today.
I would personally definitely prefer the first one.
I have also previously complained about the buildfarm showing relative
instead of absolute timestamps, for similar reasons, but I was
apparently also in the minority then.
