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 1sGhld-00GAJH-Cv for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Jun 2024 16:21:10 +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 1sGhlc-00E3eb-0V for pgsql-hackers@arkaria.postgresql.org; Mon, 10 Jun 2024 16:21:08 +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 1sGhlb-00E3eS-NC for pgsql-hackers@lists.postgresql.org; Mon, 10 Jun 2024 16:21:08 +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 1sGhla-000xj6-CP for pgsql-hackers@postgresql.org; Mon, 10 Jun 2024 16:21: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 45AGL34D740697; Mon, 10 Jun 2024 12:21:03 -0400 From: Tom Lane To: Magnus Hagander cc: Nathan Bossart , Andrew Dunstan , PostgreSQL-development Subject: Re: Non-text mode for pg_dumpall In-reply-to: References: Comments: In-reply-to Magnus Hagander message dated "Mon, 10 Jun 2024 17:45:19 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <740695.1718036463.1@sss.pgh.pa.us> Content-Transfer-Encoding: 8bit Date: Mon, 10 Jun 2024 12:21:03 -0400 Message-ID: <740696.1718036463@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Magnus Hagander writes: > On Mon, Jun 10, 2024 at 5:03 PM Nathan Bossart > wrote: >> Is there a particular advantage to that approach as opposed to just using >> "directory" mode for everything? > A gazillion files to deal with? Much easier to work with individual custom > files if you're moving databases around and things like that. > Much easier to monitor eg sizes/dates if you're using it for backups. You can always tar up the directory tree after-the-fact if you want one file. Sure, that step's not parallelized, but I think we'd need some non-parallelized copying to create such a file anyway. regards, tom lane