---
title: "Plugins"
description: "The PostgreSQL extensions and MySQL-family plugins every database offers, and what the admin user may do."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Plugins

Every database offers a fixed set of extensions and plugins. You can't add your own.

## PostgreSQL extensions

| Extension | |
| --- | --- |
| `vector` | pgvector |
| `postgis` | PostGIS |
| `pg_stat_statements` | Statement statistics |
| `pg_trgm`, `btree_gin`, `btree_gist` | Index support |
| `pgcrypto`, `hstore`, `citext`, `uuid-ossp`, `ltree`, `unaccent` | Types and functions |
| `postgres_fdw` | Foreign tables on other PostgreSQL servers |
| `pg_partman` | Partition management |
| `pg_cron` | Scheduled jobs |
| `pg_repack` | Online table and index rebuilds |
| `pgaudit` | Audit logging |
| `pg_hint_plan` | Planner hints |

Enable one in a database as `ezgh_admin`:

```sql
CREATE EXTENSION vector;
```

No superuser is needed, and other extensions are refused. `pg_stat_statements`, `pgaudit`, `pg_cron`
and `pg_hint_plan` are loaded from the start, so enabling them needs no restart. `pg_cron` runs in
the `postgres` database, where it and `pg_stat_statements` are already enabled. `pgaudit` writes to the [audit log](/databases/monitoring#logs) while the
database exports it.

`ezgh databases engine-versions -o json` lists each version's extensions.

## Percona Server plugins

- **Audit Log Filter**: writes the [audit log](/databases/monitoring#logs) while the database exports it.
- **Thread pool**: off unless you set `thread_handling` to `pool-of-threads`
  ([parameters](/databases/engines-and-versions#thread-pool)).
- **Data masking**: the masking functions are installed, and `ezgh_admin` can manage masking
  dictionaries.

## MariaDB plugins

- **`server_audit`**: writes the [audit log](/databases/monitoring#logs) while the database exports it.
- **Thread pool**: on by default ([parameters](/databases/engines-and-versions#thread-pool)).
- **Vector search** is built in.

## The admin user

`ezgh_admin` is the database's admin user on every engine. It can create databases, users and
roles, and grant what it has.

- **PostgreSQL**: `CREATEDB`, `CREATEROLE`, `pg_monitor`, `pg_signal_backend`, and ownership of what
  it creates.
- **Percona Server and MariaDB**: data and schema privileges on your databases, read-only access to
  the system schemas, users and roles, `PROCESS` and `SHOW DATABASES`, but not `SUPER`, `FILE`,
  `SYSTEM_VARIABLES_ADMIN` or replication control.

Out of reach on every engine: superuser, server file access (such as `COPY … PROGRAM`,
`LOAD DATA INFILE` and `SELECT … INTO OUTFILE`), untrusted languages, `ALTER SYSTEM` and `SET GLOBAL`.
Server settings are [parameters](/databases/engines-and-versions#parameters).

Source: https://docs.ezghcloud.com/databases/plugins/index.mdx
