Skip to content

Update RegularPostgresBackups.md #145

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.

Sign up for GitHub

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

Open
m-deck wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update RegularPostgresBackups.md #145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions articles/RegularPostgresBackups.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,9 @@

Your Postgres data on PythonAnywhere is fully protected against hardware
failure. However, we do not automatically support rolling back to a point in
time. If you want protection from accidental changes, you can set up a scheduled
task to regularly back your data up to a file, which you can re-load into
time. If you want protection from accidental changes, you can set up a [scheduled
task](https://help.pythonanywhere.com/pages/ScheduledTasks/) to regularly back
your data up to a file, which you can re-load into
Postgres at a later date.

Here's an example of a command that can dump a particular database called
Expand Down