Michael Banck <michael.ba...@credativ.de> writes:
> The same was requested in https://dba.stackexchange.com/questions/91252/
> how-to-know-when-postgresql-password-is-changed so I was wondering
> whether this would be a welcome change/addition, or whether people think
> it's not worth bothering to implement it?
This has all the same practical problems as recording object creation
times, which we're not going to do either. (You can consult the
archives for details, but from memory, the stickiest aspects revolve
around what to do during dump/reload. Although even CREATE OR REPLACE
offers interesting definitional questions. In the end there are just
too many different behaviors that somebody might want.)
I've heard that if you want to implement a password aging policy, PAM
authentication can manage that for you; but I don't know the details.
regards, tom lane
