Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEXQI-0020PS-1F for pgsql-general@arkaria.postgresql.org; Tue, 04 Jun 2024 16:54:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sEXQH-000vhG-Op for pgsql-general@arkaria.postgresql.org; Tue, 04 Jun 2024 16:54:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEXQH-000vh8-Do for pgsql-general@lists.postgresql.org; Tue, 04 Jun 2024 16:54:09 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEXQA-002KSw-Im for pgsql-general@postgresql.org; Tue, 04 Jun 2024 16:54:08 +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 454Grw4h478304; Tue, 4 Jun 2024 12:53:58 -0400 From: Tom Lane To: Adrian Klaver cc: Ron Johnson , pgsql-general Subject: Re: Purpose of pg_dump tar archive format? In-reply-to: <7005ac8c-2f83-4122-9172-04bca268f987@aklaver.com> References: <25e9749c-ff38-4832-9b26-386cac33b3d8@aklaver.com> <7005ac8c-2f83-4122-9172-04bca268f987@aklaver.com> Comments: In-reply-to Adrian Klaver message dated "Tue, 04 Jun 2024 08:33:47 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <478302.1717520038.1@sss.pgh.pa.us> Date: Tue, 04 Jun 2024 12:53:58 -0400 Message-ID: <478303.1717520038@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Adrian Klaver writes: > If you don't need the tar format then don't use it. Indeed. FTR, I think the original motivation for tar format was to have a "standard" structured output format that could be manipulated with tools other than pg_restore. Years later, we added the directory format which could be argued to serve the same purpose. But nobody particularly wanted to remove the tar functionality, especially since the two were made to be compatible: commit 7f508f1c6b515df66d27f860b2faa7b5761fa55d Author: Heikki Linnakangas Date: Sun Jan 23 23:10:15 2011 +0200 Add 'directory' format to pg_dump. The new directory format is compatible with the 'tar' format, in that untarring a tar format archive produces a valid directory format archive. regards, tom lane