Releases: silinternational/postgresql-backup-restore
Releases · silinternational/postgresql-backup-restore
Added -Sentry Notification
What's Changed
- Changed in the Branch setting and tags by @Praveenraj-K in #14
- Delete .whitesource by @briskt in #15
- Feature data img by @Praveenraj-K in #16
- Fix for Sentry by @Praveenraj-K in #17
New Contributors
- @Praveenraj-K made their first contribution in #14
- @briskt made their first contribution in #15
Full Changelog: 4.0.1...5.0.0
Use current DB owner during restore
Changes
- Constrain Python version to 3.12.3.
s3cmd
version 2.4.0 with Python 3.12.4 on Alpine 3.20 fails with anAttributeError
. - Find and use the current database owner when dropping the database during a restore operation. PostgreSQL requires the user executing a DROP DATABASE statement to be the database owner. PostgreSQL databases are initially owned by the user postgres before the ownership is set to the DB user. Restoring data to a brand new database requires a different user than restoring to an existing database.
Add option to backup to BackBlaze
Added
- Add option to backup to BackBlaze
Changed
- Switched from
docker-compose
todocker compose
Add option to backup to BackBlaze
Added
- Add option to backup to BackBlaze
Changed
- Switched from
docker-compose
todocker compose
Rollback previous release
Changed
- Revert possible breaking change with last release
Postgres 14 & Build with GitHub Actions
What's Changed
- Switch to GitHub Actions, upgrade postgres to 14 by @devon-sil in #8
Full Changelog: 3.1.1...3.2.0
Release 3.1.1
Fixes
- Changed Docker image base to python:3-alpine.
- Replaced the installation of s3cmd via "pip install" to the version in the Alpine repository.
Use $DB_USER when dropping the database
Merge pull request #6 from silinternational/develop Develop
Automated build with Codeship
User-visible change: Use $DB_ROOTUSER to drop the database.