On Tue, Dec 11, 2018 at 09:56:54AM -0500, Tom Lane wrote:
> Michael Banck <michael.banck@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 wrote a blog on this topic in 2017:
https://momjian.us/main/blogs/pgblog/2017.html#November_21_2017
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
