From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrus <kobruleht2@hot.ee>
Cc: depesz@depesz.com, pgsql-general <pgsql-general@postgresql.org>
Subject: Re: How to create directory format backup
Date: Wed, 08 Feb 2023 17:57:04 -0500
Message-ID: <3792684.1675897024@sss.pgh.pa.us> (raw)
In-Reply-To: <6da54c55-6752-ca53-cdc8-2342b2c75258@hot.ee>
References: <b27a73f5-e6e6-4076-eee6-e002528d942c@hot.ee>
<Y+Pi/vWMeo6d6uJ8@depesz.com>
<6da54c55-6752-ca53-cdc8-2342b2c75258@hot.ee>
Andrus <kobruleht2@hot.ee> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, kobruleht2@hot.ee
Subject: Re: How to create directory format backup
In-Reply-To: <3792684.1675897024@sss.pgh.pa.us>
References: <b27a73f5-e6e6-4076-eee6-e002528d942c@hot.ee> <Y+Pi/vWMeo6d6uJ8@depesz.com> <6da54c55-6752-ca53-cdc8-2342b2c75258@hot.ee> <3792684.1675897024@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox