| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andrus <kobruleht2(at)hot(dot)ee> |
| Cc: | depesz(at)depesz(dot)com, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: How to create directory format backup |
| Date: | 2023-02-08 22:57:04 |
| Message-ID: | 3792684.1675897024@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Andrus <kobruleht2(at)hot(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Katsuya Okizaki | 2023-02-08 23:10:22 | Re: How do a user-defined function that returns a table executes a query? |
| Previous Message | Katsuya Okizaki | 2023-02-08 22:54:03 | Re: How do a user-defined function that returns a table executes a query? |