3 ms·
In your opinion the two choices are "no documentation" and "badly-written documentation"?
by stavros 3y ago
In 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.
- fiddlerwoaroof 3y agoNo, whatever you do about documentation, people will either complain that you didn’t write it or they will complain that they don’t have the time to read it. This is true regardless of how good the documentation you write is.