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 1pPtNO-0007Zg-Ry for pgsql-general@arkaria.postgresql.org; Wed, 08 Feb 2023 22:57:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pPtNN-0001S3-MZ for pgsql-general@arkaria.postgresql.org; Wed, 08 Feb 2023 22:57:17 +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 1pPtNN-0001Rt-CF for pgsql-general@lists.postgresql.org; Wed, 08 Feb 2023 22:57:17 +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 1pPtNL-00035a-7x for pgsql-general@postgresql.org; Wed, 08 Feb 2023 22:57:16 +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 318Mv4UK3792685; Wed, 8 Feb 2023 17:57:04 -0500 From: Tom Lane To: Andrus cc: depesz@depesz.com, pgsql-general Subject: Re: How to create directory format backup In-reply-to: <6da54c55-6752-ca53-cdc8-2342b2c75258@hot.ee> References: <6da54c55-6752-ca53-cdc8-2342b2c75258@hot.ee> Comments: In-reply-to Andrus message dated "Wed, 08 Feb 2023 22:59:43 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3792683.1675897024.1@sss.pgh.pa.us> Date: Wed, 08 Feb 2023 17:57:04 -0500 Message-ID: <3792684.1675897024@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Andrus writes: > This file size is only 6.2 GB. If custom format is used, pg_dump creates > large file without problems. There are no file size limits. Error > message is not about this. Are you certain that the pg_dump you're using is v15, and not something pre-v14? We got rid of the 4GB limit on stat() results in v14, or so we thought. Anyway, as far as I can find pg_dump can only reach that error message via fsync_dir_recurse(), which suggests that a workaround might be to add --no-sync so it doesn't try to fsync its output. regards, tom lane