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 ) id 1lsDVM-0000Vq-P2 for pgsql-admin@arkaria.postgresql.org; Sat, 12 Jun 2021 23:57:32 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lsDVK-00060q-GK for pgsql-admin@arkaria.postgresql.org; Sat, 12 Jun 2021 23:57:30 +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 ) id 1lsDVK-00060i-62 for pgsql-admin@lists.postgresql.org; Sat, 12 Jun 2021 23:57:30 +0000 Received: from mail-oi1-x231.google.com ([2607:f8b0:4864:20::231]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1lsDVI-0006ng-4D for pgsql-admin@lists.postgresql.org; Sat, 12 Jun 2021 23:57:29 +0000 Received: by mail-oi1-x231.google.com with SMTP id s23so10172750oiw.9 for ; Sat, 12 Jun 2021 16:57:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=bICz1AfULvl4XH3+S7LE8fxibPVEY+1FeLQf9ytUurg=; b=VN2qE7zpE9RIWkHxDyyWw+BPFBEYqmZIy8kcYE5KC1Dfeb1RexXOuA7JFcMFjfVX15 rnXArlAzDk43Q+2o9QG2bvv0vtZWZymc9s5VpBc7PaYuOEFzCFrcrzP1BbADZms4amDB CUdI1ND7yBDi0vWZvlE/CYPueGgebH8o90YVZ45qFm0eC2E6v8qy0IHg5QyaMv3TaLRv xASirOG1aHn3cAhhzi+m2LrXda7ZItT8TRsqs91NTtFitEvnl5Bav+ZkjxnMQq493ufy gqIC6tpHEFYUatnPtyebFUzE8dGBBRB1K4NWndNUi4wxiQI+hjjkO2dNPiVMO2AK7Lb0 7JmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=bICz1AfULvl4XH3+S7LE8fxibPVEY+1FeLQf9ytUurg=; b=HkXcUUAuXWWp6GKxZ2IxRKlk/jdM/aebA7ltkR51Ua9xnaTf+mhxXq1IAGHY441JLI rWoe9kS0PAKNJMowfqhqpJBQ1cPRZlUIkg+fvzCnYILnJW3Rb501ldSHKoAUf1400AvL yDJz8Lc+QDbUVhGwEQM3GmXMeIonKeTPOx2YW6V18Ex/LzYf4Kf2XbBxkKWLBFKcPY2A XJGbiinzSplcN/6z2DyYdCR68olu3aa2c92KPejiMmCPzwPy5RX0eiL6L9pt1PZ3LEj8 LHpYXjDM6js4Gf/V+MXpa/BTQuU5fk0IQK5Z2BuXK2ngwoa4FXu2dM67NTUVYgcieeDj tTyQ== X-Gm-Message-State: AOAM531DWdenDnhZ6u9LiUEZZ4UyaiGySM+rG0mkBmCeQw/1wYDdF98D mdbH2EFZmJ/ezp/UXu7W60Mb+3StK/NYfQ== X-Google-Smtp-Source: ABdhPJxT7B+HxsiZWYHkAnI+Me6bO6wO8LUHmwpTDUGzIb8qWcha6LQq2f3wlCbJZL2+ackiiSUgRA== X-Received: by 2002:aca:dfc2:: with SMTP id w185mr6615181oig.91.1623542245823; Sat, 12 Jun 2021 16:57:25 -0700 (PDT) Received: from [192.168.88.10] (ip174-67-141-204.no.no.cox.net. [174.67.141.204]) by smtp.googlemail.com with ESMTPSA id g38sm2282809otg.28.2021.06.12.16.57.25 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 12 Jun 2021 16:57:25 -0700 (PDT) Subject: Re: pg_restore: warning: invalid creation date in header To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: <58342210-77b5-421a-30ed-a0a47570c7e6@gmail.com> Date: Sat, 12 Jun 2021 18:57:24 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------D4E5BF3712F46BBFAC20308B" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------D4E5BF3712F46BBFAC20308B Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit On 6/12/21 6:47 PM, Wells Oliver wrote: > 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 > pg_restore: while PROCESSING TOC: Given that it's just a warning, did the restore complete? As for the reason... since PDT is -7 to UTC, I bet the creation date is *less than* the clock date, which pg_restore warns about. -- Angular momentum makes the world go 'round. --------------D4E5BF3712F46BBFAC20308B Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit On 6/12/21 6:47 PM, Wells Oliver wrote:
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
pg_restore: while PROCESSING TOC:

Given that it's just a warning, did the restore complete?

As for the reason... since PDT is -7 to UTC, I bet the creation date is less than the clock date, which pg_restore warns about.

--
Angular momentum makes the world go 'round.
--------------D4E5BF3712F46BBFAC20308B--