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+FBWDhDHO7G-i1_n_hjRzCnUeFO+H-Czi1y10mFhRWpBrew@mail.gmail.com>
References: 
 <CAOC+FBWDhDHO7G-i1_n_hjRzCnUeFO+H-Czi1y10mFhRWpBrew@mail.gmail.com>
Comments: In-reply-to Wells Oliver <wells.oliver@gmail.com>
	message dated "Sat, 12 Jun 2021 16:47:24 -0700"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <50544.1623597209.1@sss.pgh.pa.us>
Date: Sun, 13 Jun 2021 11:13:29 -0400
Message-ID: <50545.1623597209@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/50545.1623597209%40sss.pgh.pa.us>
Precedence: bulk

Wells Oliver <wells.oliver@gmail.com> writes:
> These are the first lines when trying to restore a dump created on a
> machine in the PDT time zone, into a machine in UTC. Not sure if it
> matters, but I wanted to ask.

> pg_restore: warning: invalid creation date in header

Hmm.  Looking at the code for that, it knows nothing of timezones.
It's complaining that mktime() failed, which perhaps is because of
bad data in the archive header ... but I'm betting it has something
to do with failing to initialize all the fields of the struct tm
it passes.

However, that code's been like that a long time and we've not heard
previous reports of this.  Could you say exactly what the (receiving)
platform is?  How was pg_restore built (any special switches, etc)?
The output of pg_config on that machine might be helpful.

			regards, tom lane