Re: [HACKERS] WAL consistency check facility - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] WAL consistency check facility
Date
Msg-id CA+TgmoZXbjK4+70SbyaNKxB+eUNuPQkWGgXFY+n5Ut4jB=S2Ag@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] WAL consistency check facility  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] WAL consistency check facility
List pgsql-hackers
On Tue, Feb 14, 2017 at 5:16 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Wed, Feb 15, 2017 at 2:43 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> On Thu, Feb 9, 2017 at 8:17 PM, Michael Paquier
>> <michael.paquier@gmail.com> wrote:
>>> Please find attached a patch with those fixes.
>>
>> Committed, but I changed the copyright dates to 2016-2017 rather than
>> just 2017 since surely some of the code was originally written before
>> 2017.  Even that might not really be going back far enough, but it
>> doesn't matter too much.
>
> Just for curiosity: does the moment when the code has been written or
> committed counts? It's no big deal seeing how liberal the Postgres
> license is, but this makes me wonder...

IANAL, but I think if you ask one, he or she will tell you that what
matters is the date the work was created.  In the case of code, that
means when the code was written.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] gitlab post-mortem: pg_basebackup waiting for checkpoint
Next
From: "Higuchi, Daisuke"
Date:
Subject: [HACKERS] new high availability feature for the system with both asynchronousand synchronous replication