Horton

Re: Pasword expiration warning

Greg Sabino Mullane <htamfids@gmail.com>

View thread View on postgr.es
From: Greg Sabino Mullane <htamfids@gmail.com>
To: Chao Li <li.evan.chao@gmail.com>
Cc: Nathan Bossart <nathandbossart@gmail.com>, Euler Taveira <euler@eulerto.com>, Peter Eisentraut <peter@eisentraut.org>, Gilles Darold <gilles@darold.net>, Zsolt Parragi <zsolt.parragi@percona.com>, japin <japinli@hotmail.com>, Yuefei Shi <shiyuefei1004@gmail.com>, songjinzhou <tsinghualucky912@foxmail.com>, pgsql-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-05T14:39:53Z
Lists: pgsql-hackers 
On Wed, Feb 4, 2026 at 8:07 PM Chao Li <li.evan.chao@gmail.com> wrote:

> * Using `INT_MAX` as the upper bound feels a bit meaningless. Would it
> make sense to cap this at a more reasonable value (say 30, 60, or 180
> days)? That could help catch accidental misconfiguration — for example,
> typing `70d` instead of `7d`.
>

-1. We allow very large GUC ranges for lots of things, and don't try to
catch accidental settings. Also, 70d seems a perfectly reasonable value to
me.

--
Cheers,
Greg

Commits

  1. Add password expiration warnings.