Avoid too prominent use of "backup" on pg_dump man page
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: pgsql-docs <pgsql-docs@postgresql.org>
Date: 2024-05-29T23:11:34Z
Lists: pgsql-docs
Attachments
- 0001-doc-Avoid-too-prominent-use-of-backup-on-pg_dump-man.patch (text/plain) patch 0001
In Karen Jex's presentation today at pgconf.dev [0] one of the examples given was that users inadvertently rely on pg_dump as their primary backup tool, when better solutions exist. The pg_dump man page is arguably misleading in that it starts with "pg_dump is a utility for backing up a PostgreSQL database." I suggest toning this down a little bit. In the attached patch, I have replaced most uses of "backup" with "export" and added a short note that pg_dump is not a general-purpose backup tool. Suggestions for word-smithing welcome. [0]: https://www.pgevents.ca/events/pgconfdev2024/schedule/session/126-how-postgres-is-misused-and-abused-in-the-wild/
Commits
-
doc: Avoid too prominent use of "backup" on pg_dump man page
- 4f29394ea941 18.0 landed