Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multi-page Postgres dump fails to restore #297

Open
dshunfen opened this issue May 10, 2024 · 1 comment
Open

Multi-page Postgres dump fails to restore #297

dshunfen opened this issue May 10, 2024 · 1 comment

Comments

@dshunfen
Copy link

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:

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
Copy link
Author

Made a PR for this here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant