5 ms·
Alternatively you could use Continuous Archiving with Point In Time Recovery [1] which has been built into Postgres for a while. Once your db exceeds several t
by michelpp 3y ago
Alternatively you could use Continuous Archiving with Point In Time Recovery [1] which has been built into Postgres for a while. Once your db exceeds several tens of gigabytes dumping to SQL is just not a viable solution anymore.
[1] https://www.postgresql.org/docs/current/continuous-archiving.html https://www.postgresql.org/docs/current/continuous-archiving...
- itsthecourier 3y agoExactly, this is the way
- stavros 3y agoThis is great, I just wish it were a bit easier to set up and configure. That multi-page wall-of-text document is not looking inviting at all.
- javaunsafe2019 3y agoReally? I just read over it lying in bed for the last 15 minutes and found it super straight forward and well explained. Kudos to the pg team!
- fiddlerwoaroof 3y agoIt’s funny how you just can’t win with documentation: either “there is no documentation” or “tl;dr”
- BigJono 3y agoSurely if there's anything you don't need a 'tl;dr' for it's setting up your database backups lol. I just had a quick skim of those docs, looks like lots of paragraphs going over all of all the things that can go wrong and how to prevent them. Good. If it takes a week to read all that and set up then it takes a week. I'll take a pass on the "docker container that just does it for me" thanks.
- quest88 3y agoQueue the future “show hn: a lightweight pg backup solution”
- stavros 3y agoIn your opinion the two choices are "no documentation" and "badly-written documentation"?
- dspillett 3y agoLong does not imply bad at all, unless the tl:dr; is in response to it being a badly structured wall of text. I've not read that page from end to end, only scanned through it, but it seems perfectly good for covering the concept, with one caveat that it might not include a detail I'd put in there. Unless I missed it in my scan the page may be missing a point that seems obvious but relatively green admins might miss until they run it of backup space (or start getting larger bills for the auto-growing cloud storage they are backing up to!): your WAL based backups will grow infinitely, and restore time will grow likewise, if you don't occasionally restart your backup sequence with a fresh full backup.
- stavros 3y ago> unless the tl:dr; is in response to it being a badly structured wall of text. It is, yes. It does contain a lot of information, but the fact that it's one big wall of text makes my ADHD go do something else. Even a table of contents, or some better-structured headlines would help.
- abenga 3y ago"Badly written" is something I have never heard about official Postgres documentation.
- btown 3y agoAre there any standalone projects for this? A stable docker image that I can point to a Postgres server that can handle both archiving streamed logs to storage and populating a standby (say, on a different cloud) in real time?