Postgres extensions
Every extension a Scribase project can turn on, with the version in the engine today, what it is for, the statement that enables it and an example you can paste. Versions were read from the running engine image on October 8, 2026.
AI and vectors
| Extension | Version | What it does |
|---|---|---|
| vector | 0.8.7 | Store embeddings and find the nearest ones (pgvector, HNSW and IVFFlat indexes). |
APIs and HTTP
| Extension | Version | What it does |
|---|---|---|
| pg_graphql | 1.6.2 | A GraphQL API over your tables at /graphql/v1. |
| pg_net | 0.20.4 | Send HTTP requests from SQL, triggers and cron jobs. |
| pg_jsonschema | 0.3.4 | Check json and jsonb values against a JSON Schema in a CHECK constraint. |
Jobs, queues and partitions
| Extension | Version | What it does |
|---|---|---|
| pgmq | 1.13.0 | Message queues in SQL: send, read with a visibility timeout, archive. |
| pg_cron | 1.6 | Run SQL on a schedule written in cron syntax. |
| pg_partman | 5.5.0 | Create and drop time or number partitions for you. |
Security and secrets
| Extension | Version | What it does |
|---|---|---|
| supabase_vault | 0.3.1 | Store secrets encrypted with a key only the server can read. |
| pgcrypto | 1.3 | Hashing, password hashing and encryption functions. On by default. |
| pgaudit | 17.1 | Write detailed audit lines for the statements you choose. |
Performance
| Extension | Version | What it does |
|---|---|---|
| pg_stat_statements | 1.11 | Timing and call counts for every query shape (Insights reads it). On by default. |
| hypopg | 1.4.3 | Try an index without building it, to see if the planner would use it. |
| index_advisor | 0.2.0 | Suggest the indexes that would speed up a query. |
| pg_repack | 1.5.3 | Remove table and index bloat without long locks. |
Text search and indexing
| Extension | Version | What it does |
|---|---|---|
| pg_trgm | 1.6 | Fuzzy text search and fast LIKE and ILIKE with trigram indexes. |
| unaccent | 1.1 | Remove accents from text for search. |
| fuzzystrmatch | 1.2 | Soundex, Metaphone and Levenshtein distance. |
| btree_gin | 1.3 | GIN indexes over plain columns, for mixed indexes. |
| btree_gist | 1.7 | GiST indexes over plain columns, for exclusion constraints. |
Data types
| Extension | Version | What it does |
|---|---|---|
| uuid-ossp | 1.1 | UUID generators (v1 to v5). On by default. |
| pg_uuidv7 | 1.7 | Time-ordered UUID v7 values. |
| citext | 1.6 | Case-insensitive text, for emails and user names. |
| hstore | 1.8 | Key-value pairs in one column. |
| ltree | 1.3 | Tree paths such as categories and org charts. |
| intarray | 1.5 | Functions and indexes for integer arrays. |
| cube | 1.5 | Multi-dimensional points and boxes. |
Development
| Extension | Version | What it does |
|---|---|---|
| tablefunc | 1.0 | Crosstab and other table functions. |
| plpgsql_check | 2.10 | Lint PL/pgSQL functions before they run. |
Not offered, and why
- dblink, postgres_fdw, file_fdw: Reach outside the database (other servers or the file system).
- pageinspect, pg_surgery, pg_walinspect, amcheck: Low-level administration tools that need a superuser.
- postgis: Only on engines built with it; not on the hosted engine today.
- Untrusted languages (plpython3u, plperlu): Run arbitrary code on the server.
Extensions on Scribase
How do I turn on a Postgres extension?
Run CREATE EXTENSION in the SQL editor (each page shows the exact statement), switch it on from the Extensions page in the console, or call the API or MCP tool. Extensions that need a superuser are created for you by the platform; you never need superuser access.
Which extensions are on by default?
pgcrypto, uuid-ossp and pg_stat_statements are on in every project because the platform uses them. Everything else is off until you turn it on.
Why is an extension I need missing?
Extensions that reach outside the database (dblink, postgres_fdw, file_fdw), untrusted languages and superuser-only tools are not offered. If you need one that is not listed, tell us what you want to do with it.