diff options
author | Enrico <Enrico204@users.noreply.github.com> | 2022-08-22 20:39:59 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2022-08-22 19:39:59 +0100 |
commit | 502f7526d0588894d179731a0a130d9448588e21 (patch) | |
tree | a17194744c6a0d929181ac36c838efc4cc464565 /docs | |
parent | 9d6a2034bcf0f62dadb51cfe1471632eaa52e36c (diff) | |
download | gitea-502f7526d0588894d179731a0a130d9448588e21.tar.gz gitea-502f7526d0588894d179731a0a130d9448588e21.zip |
Fix typo in backup documentation (pgdump->pg_dump) (#20913)
This PR fixes a small typo in the backup documentation: `pgdump` command is wrong, the correct name for the backup software in PostgreSQL is `pg_dump`
Diffstat (limited to 'docs')
-rw-r--r-- | docs/content/doc/usage/backup-and-restore.en-us.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/content/doc/usage/backup-and-restore.en-us.md b/docs/content/doc/usage/backup-and-restore.en-us.md index c9c41c413c..cae097082e 100644 --- a/docs/content/doc/usage/backup-and-restore.en-us.md +++ b/docs/content/doc/usage/backup-and-restore.en-us.md @@ -62,7 +62,7 @@ The SQL dump created by `gitea dump` uses XORM and Gitea admins may prefer to us # mysql mysqldump -u$USER -p$PASS --database $DATABASE > gitea-db.sql # postgres -pgdump -U $USER $DATABASE > gitea-db.sql +pg_dump -U $USER $DATABASE > gitea-db.sql ``` ### Using Docker (`dump`) |