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.

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

Update postgres.md #231

Merged
merged 1 commit into from
Sep 9, 2024
Merged

Update postgres.md #231

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
4 changes: 2 additions & 2 deletions docs/postgres.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ And if the database is small or it is a hobby app, this should not be looked any
However, this is not acceptable for 99% of production apps as their databases are huge and maintenance time
should be as small as possible.

Rough timing for a 1Gb database can be (but your mileage may vary):
Rough timing for a 1Tb database can be (but your mileage may vary):

- 2.5h creating Heroku backup
- 0.5h downloading backup to EC2
Expand All @@ -52,7 +52,7 @@ The migration process with Bucardo looks as follows:

Maintenance downtime here can be minutes not hours or days like in p1, but no free lunches - the process is more complex.

Rough timing for a 1Gb database can be (but your mileage may vary):
Rough timing for a 1Tb database can be (but your mileage may vary):

- whatever setup time, no hurry
- 1.5 days for onetimecopy (in 1 thread) - DDL changes not allowed, but no downtime
Expand Down
Loading