matrix-docker-ansible-deploy/docs/importing-postgres.md

# Importing an existing Postgres database from another installation (optional)

Run this if you'd like to import your database from a previous installation of Synapse.
(don't forget to import your `media_store` files as well - see [the importing-media-store guide](importing-media-store.md)).


## Prerequisites

For this to work, **the database name in Postgres must match** what this playbook uses.
This playbook uses a Postgres database name of `homeserver` by default (controlled by the `matrix_postgres_db_name` variable).
If your database name differs, be sure to change `matrix_postgres_db_name` to your desired name and to re-run the playbook before proceeding.

The playbook supports importing Postgres dump files in **text** (e.g. `pg_dump > dump.sql`) or **gzipped** formats (e.g. `pg_dump | gzip -c > dump.sql.gz`).

Before doing the actual import, **you need to upload your Postgres dump file to the server** (any path is okay).


## Importing

To import, run this command (make sure to replace `<server-path-to-postgres-dump.sql>` with a file path on your server):

	ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_postgres_dump=<server-path-to-postgres-dump.sql>' --tags=import-postgres

**Note**: `<server-path-to-postgres-dump.sql>` must be a file path to a Postgres dump file on the server (not on your local machine!).
Add support for importing an existing Postgres database 2019-01-01 13:40:48 +01:00			`# Importing an existing Postgres database from another installation (optional)`

Do not refer to Synapse as "Matrix Synapse" 2019-04-23 09:20:56 +02:00			`Run this if you'd like to import your database from a previous installation of Synapse.`
Make media-store restore work with server files, not local This is a simplification and a way to make it consistent with how we do Postgres imports (see 6d89319822f4b2ecb), using files coming from the server, not from the local machine. By encouraging people NOT to use local files, we potentially avoid problems such as #34 (Github issue), where people would download `media_store` to their Mac's filesystem and case-sensitivity issues will actually corrupt it. By not encouraging local files usage, it's less likely that people would copy (huge) directories to their local machine like that. 2019-01-01 14:37:57 +01:00			(don't forget to import your `media_store` files as well - see [the importing-media-store guide](importing-media-store.md)).
Add support for importing an existing Postgres database 2019-01-01 13:40:48 +01:00

			`## Prerequisites`

			`For this to work, the database name in Postgres must match what this playbook uses.`
			This playbook uses a Postgres database name of `homeserver` by default (controlled by the `matrix_postgres_db_name` variable).
			If your database name differs, be sure to change `matrix_postgres_db_name` to your desired name and to re-run the playbook before proceeding.

			The playbook supports importing Postgres dump files in text (e.g. `pg_dump > dump.sql`) or gzipped formats (e.g. `pg_dump \| gzip -c > dump.sql.gz`).

Update documentation 2019-01-01 14:35:33 +01:00			`Before doing the actual import, you need to upload your Postgres dump file to the server (any path is okay).`
Add support for importing an existing Postgres database 2019-01-01 13:40:48 +01:00

			`## Importing`

			To import, run this command (make sure to replace `<server-path-to-postgres-dump.sql>` with a file path on your server):

			`ansible-playbook -i inventory/hosts setup.yml --extra-vars='server_path_postgres_dump=<server-path-to-postgres-dump.sql>' --tags=import-postgres`

			Note: `<server-path-to-postgres-dump.sql>` must be a file path to a Postgres dump file on the server (not on your local machine!).