Re: Pasword expiration warning - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Pasword expiration warning
Date
Msg-id CAKAnmmLW5OFZYS7DnDBpxTWq7J0eV6UaN1cxoUg=L=0k5Oug8A@mail.gmail.com
Whole thread Raw
In response to Re: Pasword expiration warning  (Chao Li <li.evan.chao@gmail.com>)
List 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

pgsql-hackers by date:

Previous
From: Henson Choi
Date:
Subject: Re: Row pattern recognition
Next
From: Fujii Masao
Date:
Subject: Re: Make wal_receiver_timeout configurable per subscription