PostGIS

Store and query spatial data in PostgreSQL with geometry and geography types, spatial functions and GiST indexes.

Enable for a database

1. Open the database in the dashboard and choose Settings.
2. Find PostGIS extension and click Enable PostGIS. Installation applies only to that database.
3. For direct connections, reconnect to load the updated search path. With transaction pooling, use schema-qualified types and functions or SET LOCAL search_path = public, armordb_postgis inside each transaction. Existing pooler server sessions may retain their previous search path.

PostGIS activation is available on existing plans without a separate extension charge. Storage and resource limits still apply. This release supports core PostGIS; raster, topology and other optional extensions are not managed by this feature.

Spatial queries

-- Works with direct and transaction-pooled connections.
BEGIN;
SET LOCAL search_path = public, armordb_postgis;
SELECT PostGIS_Version();

CREATE TABLE places (
  id bigint GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
  name text NOT NULL,
  location geometry(Point, 4326) NOT NULL
);
CREATE INDEX places_location_gist ON places USING gist (location);

INSERT INTO places (name, location)
VALUES ('Bern', ST_SetSRID(ST_MakePoint(7.4474, 46.9480), 4326));

SELECT name FROM places
WHERE ST_Contains(
  ST_MakeEnvelope(7.0, 46.0, 8.0, 47.0, 4326), location
);
COMMIT;

Permissions and migrations

Tenant roles remain non-superusers. Core PostGIS requires administrative installation, so enable it through the dashboard before running migrations instead of running CREATE EXTENSION postgis as the tenant. New installations use the administrator-owned armordb_postgis schema. The managed owner role gets schema usage and a database-specific search path. Additional roles need their own grants and search path.

For existing sessions or explicit schema references, use armordb_postgis.geometry and armordb_postgis.ST_Contains. Read the schema shown in Settings if importing a database with an existing PostGIS installation. Additive activation is idempotent; removal and version upgrades are not exposed through the dashboard.

Backups and restores

A restore needs a compatible PostgreSQL/PostGIS image on the destination. ArmorDB restores prepare the managed extension before restoring your spatial tables and indexes. The packaged spatial_ref_sys catalogue remains administrator-owned. Imported installations in another schema require a separate migration. Preserve extension schemas, privileges and search paths when migrating. After restoring, verify PostGIS_Version() and your spatial queries from a new application connection.

Availability and replicas

Founder, Pro and Scale currently operate on a best-effort basis, without a contractual uptime guarantee or service-credit SLA. Read replicas and standby services are planned but not currently implemented or available; pricing has not been set. PostGIS support does not change that availability model.