Re: Pasword expiration warning

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Gilles Darold <gilles(at)darold(dot)net>, Japin Li <japinli(at)hotmail(dot)com>, Yuefei Shi <shiyuefei1004(at)gmail(dot)com>, songjinzhou <tsinghualucky912(at)foxmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, liu xiaohui <liuxh(dot)zj(dot)cn(at)gmail(dot)com>, Steven Niu <niushiji(at)gmail(dot)com>
Subject: Re: Pasword expiration warning
Date: 2026-02-04 17:44:06
Message-ID: CAN4CZFNSqhRbkh_2MaZNysACf1T-A7hW+=t0tQTUX+Mar0_ymA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2026-02-04 17:54:11 Re: Show expression of virtual columns in error messages
Previous Message Sergey Soloviev 2026-02-04 17:33:44 Re: Introduce Index Aggregate - new GROUP BY strategy