ConceptsDatastores
What a datastore cannot do
A datastore is one container. After its creation, you can change only its limits.
New datastore. Create a datastore with the new version.
1 / 3
The limits
| What | The rule |
|---|---|
| One container | A datastore has no replica, no high availability and no connection pooler. |
| No change after creation | You can change only the memory and CPU limits. There is no version upgrade, no new password and no new name. |
| No disk quota | The volume can grow until the disk of the server is full. |
| Two kinds | Ferry has only Postgres and Redis datastores. |
Other databases
Run each other database as a private service with a disk.
A blueprint can list a different version, database or user for a datastore that exists. Then Ferry only gives a warning. But Ferry does change the limits.
pg_dump and psql are tools of Postgres. See Back up a datastore for a pg_dump command.