Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1lsUSd-0001Uz-8L
	for pgsql-admin@arkaria.postgresql.org; Sun, 13 Jun 2021 18:03:51 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1lsUSa-0007hp-CD
	for pgsql-admin@arkaria.postgresql.org; Sun, 13 Jun 2021 18:03:48 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1lsUSa-0007hg-3U
	for pgsql-admin@lists.postgresql.org; Sun, 13 Jun 2021 18:03:48 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1lsUSS-00077p-Qk
	for pgsql-admin@postgresql.org; Sun, 13 Jun 2021 18:03:46 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 15DI3cBs113490;
	Sun, 13 Jun 2021 14:03:38 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <wells.oliver@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: pg_restore: warning: invalid creation date in header
In-reply-to: 
 <CAOC+FBX1_w=kkZ28t9cyc1STd5CPfczrTk2tBkHApzJz4he0Yw@mail.gmail.com>
References: 
 <CAOC+FBWDhDHO7G-i1_n_hjRzCnUeFO+H-Czi1y10mFhRWpBrew@mail.gmail.com>
 <50545.1623597209@sss.pgh.pa.us> <52307.1623599837@sss.pgh.pa.us>
 <CAOC+FBXMZaRa7msrbCshJPLyA7i17n_=a4DhLiHZZEqesncwKw@mail.gmail.com>
 <52961.1623600745@sss.pgh.pa.us>
 <CAOC+FBXAPDztW3o7DzVHeQFyaOe5Z-k3K16xtCSXqWTa03k3qA@mail.gmail.com>
 <55481.1623604303@sss.pgh.pa.us>
 <CAOC+FBX1_w=kkZ28t9cyc1STd5CPfczrTk2tBkHApzJz4he0Yw@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Sun, 13 Jun 2021 10:27:17 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <113488.1623607418.1@sss.pgh.pa.us>
Date: Sun, 13 Jun 2021 14:03:38 -0400
Message-ID: <113489.1623607418@sss.pgh.pa.us>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/113489.1623607418%40sss.pgh.pa.us>
Precedence: bulk

Wells Oliver <wells.oliver@gmail.com> writes:
> I've still got a lot of testing to do, but it does not look like materially
> impacted the restored data.. but definitely caught my eye.

No, it doesn't affect the validity of the restored data at all.
If you did "pg_restore -l", it would print a bogus archive creation
date, but I'm pretty sure we don't use the file timestamp otherwise.

			regards, tom lane