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 1lRiN6-0006yc-B1 for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Mar 2021 21:27:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1lRiN4-0000lp-4P for pgsql-bugs@arkaria.postgresql.org; Wed, 31 Mar 2021 21:27:26 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lRiN3-0000lc-UK for pgsql-bugs@lists.postgresql.org; Wed, 31 Mar 2021 21:27:25 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1lRiMx-0002qV-Ng for pgsql-bugs@lists.postgresql.org; Wed, 31 Mar 2021 21:27:24 +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 12VLRBpQ3331061; Wed, 31 Mar 2021 17:27:11 -0400 From: Tom Lane To: skoposov@ed.ac.uk cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16951: pg_restore segfaults on custom format piped from a different version of PG In-reply-to: <16951-a4dd68cf0de23048@postgresql.org> References: <16951-a4dd68cf0de23048@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Wed, 31 Mar 2021 20:06:01 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3331059.1617226031.1@sss.pgh.pa.us> Date: Wed, 31 Mar 2021 17:27:11 -0400 Message-ID: <3331060.1617226031@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > I have a reproducible case of segfaulting pg_restore when trying to restore > from pg_dump of a different version. Specifically at least pg_restore from > 10 crashes from pg_dump 12. When I try that I get pg_restore: [archiver] unsupported version (1.14) in file header and that test is done first thing in ReadHead(), before the place you identify. I suspect you are dealing with a corrupt archive file, not a version mismatch. regards, tom lane