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: <50545.1623597209@sss.pgh.pa.us>
References: 
 <CAOC+FBWDhDHO7G-i1_n_hjRzCnUeFO+H-Czi1y10mFhRWpBrew@mail.gmail.com>
 <50545.1623597209@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Sun, 13 Jun 2021 11:13:29 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <52306.1623599837.1@sss.pgh.pa.us>
Date: Sun, 13 Jun 2021 11:57:17 -0400
Message-ID: <52307.1623599837@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/52307.1623599837%40sss.pgh.pa.us>
Precedence: bulk

I wrote:
> 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.

After reading the mktime man page, I take that back --- it's not
supposed to consider the passed-in values of the tm_wday and tm_yday
fields.  The only documented reason for mktime to fail is if the
supplied values map to something outside the range of time_t,
which seems a tad unlikely.  It'd be interesting perhaps to see
the raw header of your dump file, along the lines of
"od -c dumpfile | head".

			regards, tom lane