Horton

Re: Pasword expiration warning

Zsolt Parragi <zsolt.parragi@percona.com>

View thread View on postgr.es
From: Zsolt Parragi <zsolt.parragi@percona.com>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Peter Eisentraut <peter@eisentraut.org>, Gilles Darold <gilles@darold.net>, Japin Li <japinli@hotmail.com>, Yuefei Shi <shiyuefei1004@gmail.com>, songjinzhou <tsinghualucky912@foxmail.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>, Andrew Dunstan <andrew@dunslane.net>, Tom Lane <tgl@sss.pgh.pa.us>, liu xiaohui <liuxh.zj.cn@gmail.com>, Steven Niu <niushiji@gmail.com>
Date: 2026-02-04T17:44:06Z
Lists: pgsql-hackers 
> > 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.

Commits

  1. Add password expiration warnings.