mirror of
https://github.com/eduardolat/pgbackweb.git
synced 2026-04-25 05:35:57 +03:00
[GH-ISSUE #36] [Feature] pg_dump optimization #27
Labels
No labels
bug
confirmed next step
duplicate
enhancement
help wanted
in progress
in progress
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/pgbackweb#27
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @berkayyildi on GitHub (Sep 4, 2024).
Original GitHub issue: https://github.com/eduardolat/pgbackweb/issues/36
Hello eduardo,
This is one of the project which I want to develop. Thanks for developing this project.
I couldn't try it now my environments are not ready now, but I want to give suggestion to you.
pg_dump without parameter is not efficient, as I see in project codes you get dump then compress it.
Instead of this, you can use directory format backup.
https://www.reddit.com/r/PostgreSQL/comments/1ckewh8/comment/l2mwerg/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
pg_dump -v -Fd -Z1 --blobs --jobs=40
This is the most efficient backup method most of the time. And you don't need additional compression.
I think adding these methods to UI (plain backup or job count with directory format) will decrease backup size and increase backup speed for TB size databases.
Thanks