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.

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

Update postgresql data migration guide #3223

Merged
merged 2 commits into from
Jan 27, 2022
Merged
Changes from all commits
Commits
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
11 changes: 8 additions & 3 deletions docs/database.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,8 @@ data, configure the new PostgreSQL instance, and restore the data.

- Importer for the old PostgreSQL database instance is stopped
- The new PostgreSQL database instance
- An ubuntu virtual machine with fast network speed connections to both PostgreSQL database instances. The instance should also have
enough free disk space for the database dump
- An ubuntu virtual machine with fast network speed connections to both PostgreSQL database instances. The instance
should also have enough free disk space for the database dump

### Backup

Expand Down Expand Up @@ -53,11 +53,16 @@ The following configuration needs to be applied to the database instance to impr

```
checkpoint_timeout = 30m
maintenance_work_mem = 2GB
max_parallel_maintenance_workers = 4
max_wal_size = 512GB
temp_file_limit = 2147483647kB
```

Note: once the data is restored, revert the values back for normal operation.
Note:
- Not all flags are available in managed database services. For example, `max_parallel_maintenance_workers` is not
available in Google Cloud SQL.
- Once the data is restored, revert the values back for normal operation.

### Restore

Expand Down