specific.hcl gives you a local database during specific dev and a managed production database on deploy.
specific.hcl
Connection attributes
Reference these inenv blocks:
| Attribute | Description |
|---|---|
url | Full connection string (for example, postgres://user:pass@host:5432/dbname). |
host | Database host. |
port | Database port. |
user | Database user. |
password | Database password. |
name | Database name. |
direct_url | Non-pooled connection string, bypassing the connection pooler. Use when you need a direct connection (for example, Prisma’s directUrl). |
direct_host | Non-pooled database host. |
Extensions
The following PostgreSQL extensions are available in both development and production. Enable each withCREATE EXTENSION in a migration:
| Extension | Enable with | Use for |
|---|---|---|
| pgvector | CREATE EXTENSION vector; | Vector similarity search. |
| pg_search | CREATE EXTENSION pg_search; | Full-text search with BM25 ranking, powered by ParadeDB. |
| PostGIS | CREATE EXTENSION postgis; | Geospatial queries and indexing. |
| pg_trgm | CREATE EXTENSION pg_trgm; | Trigram-based fuzzy text matching and LIKE/ILIKE indexes. |
| ltree | CREATE EXTENSION ltree; | Hierarchical structures: categories, org charts, taxonomies. |
| pgRouting | CREATE EXTENSION pgrouting CASCADE; | Routing and network analysis (requires PostGIS, installed by CASCADE). |
ltree for hierarchies and pgrouting for weighted networks and shortest-path queries. Apache AGE and Cypher queries are not supported.
Querying the database
Local development
Usespecific psql to connect to a development database. The database is started automatically if it isn’t running.
Production
Usespecific query --db <name> to run read-only Postgres SQL against a deployed environment’s database:
INSERT, UPDATE, DELETE, and DDL are rejected (the query runs inside a read-only transaction). Without --db, specific query targets observability data instead. You can also browse data and manage the database from the dashboard.
Schema migrations
For zero-downtime schema migrations, enable Reshape:specific.hcl
pre_deploy hook; run specific docs integrations/prisma or specific docs integrations/drizzle for setup guidance.