Re: pgsql: Allow some recovery parameters to be changed with reload

Greetings,

* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > On 2019-Feb-08, Michael Paquier wrote:
> >> The timestamp of this commit is a bit messed up:
> >> commit: 13b89f96d07ad3da67b57f66c134c3609bd3e98f
> >> author: Peter Eisentraut <peter(at)eisentraut(dot)org>
> >> date: Mon, 4 Feb 2019 09:28:17 +0100
> >> committer: Peter Eisentraut <peter(at)eisentraut(dot)org>
> >> date: Thu, 7 Feb 2019 08:34:48 +0100
> >>
> >> Perhaps you overlooked a --reset-author switch?
>
> > I don't think we actually have a rule about these timestamps, and I
> > don't think we really care, do we?
>
> Yeah, if you want to see a sequence of dates that makes sense,
> you need to look at the commit-date. Whether the author-date
> closely matches that depends on the particular committer's
> workflow.

While I agree that we don't really have a formal policy, there are
certainly some who do (or, at least did) seem to care quite a bit about
this and that's why I've been using '--ignore-date' for quite some time
in my workflow:

https://www.postgresql.org/message-id/CA%2BTgmobEgs1%3DAT0_SRvf6K9XrG7QAUyRNeuv5D9oaXrmpST9fw%40mail.gmail.com

Thanks!

Stephen