Re: Pasword expiration warning

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Euler Taveira <euler(at)eulerto(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Gilles Darold <gilles(at)darold(dot)net>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, japin <japinli(at)hotmail(dot)com>, Yuefei Shi <shiyuefei1004(at)gmail(dot)com>, songjinzhou <tsinghualucky912(at)foxmail(dot)com>, pgsql-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-05 14:39:53
Message-ID: CAKAnmmLW5OFZYS7DnDBpxTWq7J0eV6UaN1cxoUg=L=0k5Oug8A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Feb 4, 2026 at 8:07 PM Chao Li <li(dot)evan(dot)chao(at)gmail(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-02-05 14:40:49 Re: Make wal_receiver_timeout configurable per subscription
Previous Message Henson Choi 2026-02-05 14:28:37 Re: Row pattern recognition