Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dbbackup.db.postgres typo fix #341

Merged
merged 1 commit into from
Sep 19, 2020
Merged

dbbackup.db.postgres typo fix #341

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/databases.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -130,8 +130,8 @@ MySQL uses by default :class:`dbbackup.db.mysql.MysqlDumpConnector`. It uses
PostgreSQL
----------

Postgres uses by default :class:`dbbackup.db.postgres.PgDumpConnector`, but
we advise you to use :class:`dbbackup.db.postgres.PgDumpBinaryConnector`. The
Postgres uses by default :class:`dbbackup.db.postgresql.PgDumpConnector`, but
we advise you to use :class:`dbbackup.db.postgresql.PgDumpBinaryConnector`. The
first one uses ``pg_dump`` and ``pqsl`` for its job, creating RAW SQL files.

The second uses ``pg_restore`` with binary dump files.
Expand Down Expand Up @@ -162,7 +162,7 @@ Default: ``True``
PostGIS
-------

Set in :class:`dbbackup.db.postgres.PgDumpGisConnector`, it does the same as
Set in :class:`dbbackup.db.postgresql.PgDumpGisConnector`, it does the same as
PostgreSQL but launchs ``CREATE EXTENSION IF NOT EXISTS postgis;`` before
restore database.

Expand Down