| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-committers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pgsql: Allow some recovery parameters to be changed with reload |
| Date: | 2019-02-08 16:31:13 |
| Message-ID: | 19792.1549643473@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2019-02-08 17:29:17 | Re: pgsql: Remove references to Majordomo |
| Previous Message | Peter Eisentraut | 2019-02-08 15:47:40 | Re: pgsql: Allow some recovery parameters to be changed with reload |