My team is seeing that when a Postgres dump exceeds the 100MB file size for a single page, and gets separated into two pages, the restore fails. I've confirmed by removing some of the extra data on the database and doing a dump (which brings the file size down to just under 100MB, and a single page), I'm able to restore.
The restore fails with messages like:
ERROR: relation "public.data_historical" does not exist
LINE 1: INSERT INTO public.data_historical (data_ptr_id,...)
What other information can I provide to help to debug this? I'd look into this myself and push a fix, but I don't really know where to start.
dshunfen
commented
3 months ago
Description
My team is seeing that when a Postgres dump exceeds the 100MB file size for a single page, and gets separated into two pages, the restore fails. I've confirmed by removing some of the extra data on the database and doing a dump (which brings the file size down to just under 100MB, and a single page), I'm able to restore.
The restore fails with messages like:
What other information can I provide to help to debug this? I'd look into this myself and push a fix, but I don't really know where to start.