Re: Record last password change

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Michael Banck <michael(dot)banck(at)credativ(dot)de>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Record last password change
Date: 2019-01-05 19:23:38
Message-ID: 29456.1546716218@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
>> 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 disagree with these being serious practical problems- we just need to
> decide which was to go when it comes to dump/restore here and there's an
> awful lot of example systems out there to compare to for this case.

Yeah, an awful lot of systems with an awful lot of different behaviors.
This doesn't exactly refute my point.

For the specific case of password aging, it's possible we could agree
on a definition, but that remains to be seen.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2019-01-05 19:41:14 Re: Grant documentation about "all tables"
Previous Message Tom Lane 2019-01-05 19:18:27 Re: Record last password change