添加 mysql redis postgres 插件
This commit is contained in:
4
plugins/postgres/docs/README.md
Normal file
4
plugins/postgres/docs/README.md
Normal file
@@ -0,0 +1,4 @@
|
||||
# Extra Documentation
|
||||
|
||||
The documentation in this folder is supplemental to using this plugin. It is injected automatically into the plugin's readme during documentation generation.
|
||||
|
||||
13
plugins/postgres/docs/create.md
Normal file
13
plugins/postgres/docs/create.md
Normal file
@@ -0,0 +1,13 @@
|
||||
Official Postgres "$DOCKER_BIN" image ls does not include postgis extension (amongst others). The following example creates a new postgres service using `postgis/postgis:13-3.1` image, which includes the `postgis` extension.
|
||||
|
||||
```shell
|
||||
# use the appropriate image-version for your use-case
|
||||
dokku postgres:create postgis-database --image "postgis/postgis" --image-version "13-3.1"
|
||||
```
|
||||
|
||||
To use pgvector instead, run the following:
|
||||
|
||||
```shell
|
||||
# use the appropriate image-version for your use-case
|
||||
dokku postgres:create pgvector-database --image "pgvector/pgvector" --image-version "pg17"
|
||||
```
|
||||
5
plugins/postgres/docs/export.md
Normal file
5
plugins/postgres/docs/export.md
Normal file
@@ -0,0 +1,5 @@
|
||||
Note that the export will result in a file containing the binary postgres export data. It can be converted to plain text using `pg_restore` as follows
|
||||
|
||||
```shell
|
||||
pg_restore data.dump -f plain.sql
|
||||
```
|
||||
30
plugins/postgres/docs/upgrade.md
Normal file
30
plugins/postgres/docs/upgrade.md
Normal file
@@ -0,0 +1,30 @@
|
||||
Postgres does not handle upgrading data for major versions automatically (eg. 11 => 12). Upgrades should be done manually. Users are encouraged to upgrade to the latest minor release for their postgres version before performing a major upgrade.
|
||||
|
||||
While there are many ways to upgrade a postgres database, for safety purposes, it is recommended that an upgrade is performed by exporting the data from an existing database and importing it into a new database. This also allows testing to ensure that applications interact with the database correctly after the upgrade, and can be used in a staging environment.
|
||||
|
||||
The following is an example of how to upgrade a postgres database named `lollipop-11` from 11.13 to 12.8.
|
||||
|
||||
```shell
|
||||
# stop any linked apps
|
||||
dokku ps:stop linked-app
|
||||
|
||||
# export the database contents
|
||||
dokku postgres:export lollipop-11 > /tmp/lollipop-11.export
|
||||
|
||||
# create a new database at the desired version
|
||||
dokku postgres:create lollipop-12 --image-version 12.8
|
||||
|
||||
# import the export file
|
||||
dokku postgres:import lollipop-12 < /tmp/lollipop-11.export
|
||||
|
||||
# run any sql tests against the new database to verify the import went smoothly
|
||||
|
||||
# unlink the old database from your apps
|
||||
dokku postgres:unlink lollipop-11 linked-app
|
||||
|
||||
# link the new database to your apps
|
||||
dokku postgres:link lollipop-12 linked-app
|
||||
|
||||
# start the linked apps again
|
||||
dokku ps:start linked-app
|
||||
```
|
||||
Reference in New Issue
Block a user