aboutsummaryrefslogtreecommitdiff
path: root/src/include/postgres_ext.h
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2024-07-31 07:57:47 +0200
committerPeter Eisentraut <peter@eisentraut.org>2024-07-31 07:57:47 +0200
commit4f29394ea941f688fd4faf7260d2c198931ca797 (patch)
tree38169b50041091d1bb21e434b7f078e61ef44462 /src/include/postgres_ext.h
parent73275f093f8969f4d2353fcc803377350aa650f6 (diff)
downloadpostgresql-4f29394ea941f688fd4faf7260d2c198931ca797.tar.gz
postgresql-4f29394ea941f688fd4faf7260d2c198931ca797.zip
doc: Avoid too prominent use of "backup" on pg_dump man page
Some 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." This tones this down a little bit, by replacing most uses of "backup" with "export" and adding a short note that pg_dump is not a general-purpose backup tool. Discussion: https://www.postgresql.org/message-id/flat/70b48475-7706-4268-990d-fd522b038d96%40eisentraut.org
Diffstat (limited to 'src/include/postgres_ext.h')
0 files changed, 0 insertions, 0 deletions