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

From Michael Paquier
Subject Re: [HACKERS] WAL consistency check facility
Date
Msg-id CAB7nPqTggEqZAwjw9zs1v=4TCQcTtm3+fvuyAoVMOZGX2cVCYA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] WAL consistency check facility  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] WAL consistency check facility
List pgsql-hackers
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...
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] renaming pg_resetxlog to pg_resetwal has broken pg_upgrade.
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] Skipping PgStat_FunctionCallUsage for many expressions