Both pg_dump and pg_basebackup are supported ways to backup the database #221
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are pros and cons to both logical and physical backups and in fact people should probably plan on doing both types of backups.
Physical/pg_dump for table or database exports for testing, upgrades, and for disaster recovery. It's slower but generally smaller.
Logical/pg_basebackup for cluster backups and versatility to restore from point in time or from standbys. It's also much faster.
See also:
https://www.enterprisedb.com/postgresql-database-backup-recovery-what-works-wal-pitr