5 ms·
If you are using postgres, configure it to keep the WAL logs for at least 24 hours. They could have used point-in-time recovery to not lose any data from this
by Negitivefrags 6y ago
If you are using postgres, configure it to keep the WAL logs for at least 24 hours.
They could have used point-in-time recovery to not lose any data from this at all.
- yjftsjthsd-h 6y agoIf you can do this, then yes by all means do it, but that has significant impact on disk usage.
- koolba 6y agoIt doesn’t have to be local. In fact it shouldn’t be local anyway as backups accessible to be deleted from the source aren’t real backups any way. You can the restore from a recent base backup and roll forward the WAL to just before the snafu.
- yjftsjthsd-h 6y agoYeah, but that can still create a situation where you can create WALs faster than they're uploaded. (And if there's a good solution to that, I'm interested, because we ran a server out of disk this way last month at work)