| ▲ | matt-p 6 days ago |
| no PITB, but mostly just 'it's hassle' for the application server I literally don't need backups, just automated provisioning/docker container etc. Adding postgres then means I need full backups including PITB because I don't even want to lose an hours data. |
|
| ▲ | doganugurlu 5 days ago | parent [-] |
| Or use SQLite and your backups are literally a copy of a file. You can abuse git for it if you really want to cut corners. |
| |
| ▲ | vanviegen 5 days ago | parent [-] | | Only if you can freeze your application for that long, in which case your statement is true for all non-broken databases. | | |
| ▲ | markusw 4 days ago | parent | next [-] | | You can easily do consistent backup on live databases. There’s a backup command and API. | | | |
| ▲ | wild_egg 5 days ago | parent | prev [-] | | It only freezes your application if you've misconfigured it. | | |
| ▲ | vanviegen 4 days ago | parent [-] | | If you want to backup your database using just a file copy, you'd better freeze your database if you value your data. Or use a fancy snapshotting filesystem. |
|
|
|