Role
Enabled by default
PostGIS in the PostGIS stack
This page explains what PostGIS means in the PostGIS stack: how it is included, which base service it uses, and how it connects to the rest of the stack.
PostGIS is enabled by default in instances created from the PostGIS stack, but it is not treated as a core required service.
Base service
PostGIS
Type
db
Stack fit
How PostGIS fits into this stack
PostGIS is enabled by default in instances created from the PostGIS stack, but it is not treated as a core required service.
This stack service is based on PostGIS and keeps the service-specific setup for PostGIS in one place.
Version policy
Available versions include 18.
Inclusion
Enabled by default: Yes
Required: No
Primary: No
Connections
No explicit service links are defined for this stack service.
Storage
data: 20 GB
Stack-specific technical details
Review the operational capabilities exposed by PostGIS inside this stack, including backups, imports, configs, settings, cron, actions, storage, and service links where they exist.
Backups
Protect service data with repeatable backup workflows that stay attached to the stack.
Default database backup
Imports and migration
Bring working data into another environment or onboard existing workloads faster with stack-defined import flows.
Database import
Import from a backup archive, uploaded file, or public URL depending on the service workflow.
Configs
Keep service config files versioned with the stack instead of rebuilding them per environment.
PostgreSQL config
Volumes
Provision the persistent storage and shared volume relationships the stack expects.
Data
Size: 10 GB.