Select a documentation version: <button class="button button-with-icon cloud-select-dropdown__button button-primary" aria-haspopup="true">16.3.0</button>

- [Current (18.4.0)](https://docs.cloud.google.com/alloydb/omni/containers/current/docs/reference/extensions.md.txt)
- [18.4.0](https://docs.cloud.google.com/alloydb/omni/containers/18.4.0/docs/reference/extensions.md.txt)
- [18.3.0](https://docs.cloud.google.com/alloydb/omni/containers/18.3.0/docs/reference/extensions.md.txt)
- [18.1.0](https://docs.cloud.google.com/alloydb/omni/containers/18.1.0/docs/reference/extensions.md.txt)
- [17.10.0](https://docs.cloud.google.com/alloydb/omni/containers/17.10.0/docs/reference/extensions.md.txt)
- [17.9.0](https://docs.cloud.google.com/alloydb/omni/containers/17.9.0/docs/reference/extensions.md.txt)
- [17.7.0](https://docs.cloud.google.com/alloydb/omni/containers/17.7.0/docs/reference/extensions.md.txt)
- [17.5.0](https://docs.cloud.google.com/alloydb/omni/containers/17.5.0/docs/reference/extensions.md.txt)
- [16.14.0](https://docs.cloud.google.com/alloydb/omni/containers/16.14.0/docs/reference/extensions.md.txt)
- [16.13.0](https://docs.cloud.google.com/alloydb/omni/containers/16.13.0/docs/reference/extensions.md.txt)
- [16.11.0](https://docs.cloud.google.com/alloydb/omni/containers/16.11.0/docs/reference/extensions.md.txt)
- [16.9.0](https://docs.cloud.google.com/alloydb/omni/containers/16.9.0/docs/reference/extensions.md.txt)
- [16.8.0](https://docs.cloud.google.com/alloydb/omni/containers/16.8.0/docs/reference/extensions.md.txt)
- [16.3.0](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt)
- [15.18.0](https://docs.cloud.google.com/alloydb/omni/containers/15.18.0/docs/reference/extensions.md.txt)
- [15.17.0](https://docs.cloud.google.com/alloydb/omni/containers/15.17.0/docs/reference/extensions.md.txt)
- [15.15.0](https://docs.cloud.google.com/alloydb/omni/containers/15.15.0/docs/reference/extensions.md.txt)
- [15.13.0](https://docs.cloud.google.com/alloydb/omni/containers/15.13.0/docs/reference/extensions.md.txt)
- [15.12.0](https://docs.cloud.google.com/alloydb/omni/containers/15.12.0/docs/reference/extensions.md.txt)
- [15.7.1](https://docs.cloud.google.com/alloydb/omni/containers/15.7.1/docs/reference/extensions.md.txt)
- [15.7.0](https://docs.cloud.google.com/alloydb/omni/containers/15.7.0/docs/reference/extensions.md.txt)

<br />

The following table lists all of the extensions supported by AlloyDB Omni 16.3.0.

<br />

All of these extensions are available on every AlloyDB Omni
instance. To enable any of them, see [Enable an extension](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#enable).

> [!NOTE]
> **Note:** Some extensions require additional steps before you can enable them---typically, by [setting one or more database
> flags](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/configure-database-flags) on your instances.

| Extension | Description |
|---|---|
| `alloydb_ai_nl` | Provides functions to securely query data using natural language from your application. |
| `alloydb_password_validation` | Provides functions to [set and manage password policies](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/manage-password-policy.md.txt) for AlloyDB Omni. |
| `alloydb_scann` | Provides features for [improving vector query performance]() with the ScaNN index. |
| `amcheck` | Provides functions for verifying the logical consistency of the structure of relations, enabling the `pg_amcheck` application to check for corruption. |
| `anon` | Helps you hide or replace personally identifiable information (PII) or commercially sensitive data. > [!IMPORTANT] > **Important:** Before you can use the `CREATE EXTENSION` command to enable this extension, you must add the `anon` extension into [the > `shared_preload_libraries` parameter](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), and you must ensure that the `anon` extension is loaded by restarting the database. In addition, install the `pgcrypto` extension before installing the `anon` extension. |
| `auto_explain` | Enables automatic logging of execution plans of slow statements, for troubleshooting and more. It provides an automated way to perform the functionality of the `EXPLAIN` command. > [!IMPORTANT] > **Important:** Before you can use the `LOAD` command to enable this extension, you must first add the `auto_explain` extension into [the > `shared_preload_libraries` parameter](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), and you must ensure that the `auto_explain` extension is loaded by restarting the database. |
| `autoinc` | Provides functions for incrementing fields automatically. This trigger stores the next value of a sequence into an integer field. |
| `bloom` | Provides an index access method based on Bloom filters. |
| `btree_gin` | Provides sample GIN operator classes that implement B-tree equivalent behavior. |
| `btree_gist` | Provides GiST index operator classes that implement B-tree equivalent behavior. |
| `citext` | Provides a case-insensitive character string type `citext`. |
| `cube` | Implements a data type `cube` for representing multidimensional cubes. |
| `dblink` | Provides functions to connect to PostgreSQL databases from within a database session. |
| `dict_int` | An add-on dictionary template for full-text search that controls the indexing of integers. |
| `dict_xsyn` | An add-on dictionary template that controls string indexing for full-text search. |
| `earthdistance` | Provides two approaches to calculating great circle distances on the surface of the Earth. |
| `fuzzystrmatch` | Provides several functions to determine similarities and distance between strings. |
| `google_columnar_engine` | Provides the columnar engine feature of AlloyDB Omni, which handles HTAP (hybrid transactional analytical processing) and OLAP (online analytical processing) workloads very efficiently. > [!IMPORTANT] > **Important:** Before you can use `CREATE EXTENSION` to enable this extension, you must first [set the database flag](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/database-flags.md.txt) `google_columnar_engine.enabled` to the value `on` in the AlloyDB Omni instance where you want to use the extension. |
| `google_db_advisor` | Provides the index advisor feature of AlloyDB Omni, which recommends indexes to speed up query processing. |
| `google_ml_integration` | Provides functions you use to access Vertex AI prediction endpoints to get predictions in SQL. |
| `hstore` | Implements the `hstore` data type for storing sets of key/value pairs within a single PostgreSQL value. |
| `hypopg` | Provides support for hypothetical indexes. |
| `insert_username` | Provides functions for storing the current user's name into a text field. You can use this function to track which user last modified a row in a database table. |
| `intagg` | Provides an integer aggregator and an enumerator. |
| `intarray` | Provides a set of functions and operators for manipulating null-free arrays of integers and performing indexed searches on them. |
| `ip4r` | Provides data types for IPv4/v6 addresses, and address ranges, plus index support. |
| `isn` | Provides data types for some international product numbering standards. |
| `lo` | Support for managing Large Objects (also called LOs or BLOBs). |
| `ltree` | Implements a data type `ltree` for representing labels of data stored in a hierarchical tree-like structure. |
| `moddatetime` | Provides functions for storing the current time into a `timestamp` field. You can use this function to track the last time that a row in a database table was modified. |
| `pageinspect` | Inspects the contents of database pages at a low level. |
| `pg_bigm` | Provides full text search capability in PostgreSQL using 2-gram (bigram) indexes for faster full text searches. > [!IMPORTANT] > **Important:** Before you can use the `CREATE EXTENSION` command to enable this extension, you must first add the `pg_bigm` extension into [the > `shared_preload_libraries` parameter\>](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), and you must ensure that the `pg_bigm` extension is loaded by restarting the database. |
| `parameterized_views` | Provides functions that add a security layer when natural language queries are translated to SQL queries. This extension works together with the `alloydb_ai_nl` extension. |
| `pg_buffercache` | Provides a means for examining what's happening in the shared buffer cache in real time. |
| `pg_cron` | Provides a cron-based job scheduler for PostgreSQL that runs inside the database as an extension. It uses the same syntax as regular `cron`, but it lets you schedule PostgreSQL commands directly from the database. > [!IMPORTANT] > **Important:** Before you can use the `CREATE EXTENSION` command to enable this extension, you must first add the `pg_cron` extension into [the > `shared_preload_libraries` parameter](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), and you must ensure that the `pg_cron` extension is loaded by restarting the database. |
| `pg_freespacemap` | Examines the free space map (FSM). |
| `pg_hint_plan` | Helps you improve PostgreSQL execution plans using hints, which are descriptions in SQL comments. > [!IMPORTANT] > **Important:** Before you can use the `CREATE EXTENSION` command to enable this extension, you must first add the `pg_hint_plan` extension into [the > `shared_preload_libraries` parameter\>](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), and you must ensure that the `pg_hint_plan` extension is loaded by restarting the database. |
| `pg_ivm` | Provides Incremental View Maintenance (IVM) feature for PostgreSQL. |
| `pg_partman` | Lets you create and manage time-based and serial-based table partition sets. |
| `pg_prewarm` | Provides a convenient way to load relation data into either the operating system buffer cache or the PostgreSQL buffer cache. |
| `pg_proctab` | Lets you use [pg_top](https://pg_top.gitlab.io/) with AlloyDB Omni, and generate reports from the operating system process table. |
| `pg_repack` | Lets you remove bloat from tables and indexes. Optionally, lets you perform an online CLUSTER (order tables by cluster index). |
| `pg_similarity` | Provides support for similarity queries on PostgreSQL. |
| `g_stats` | Enables one to [optimize database performance](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/optimize-database-performance-compare-snapshots.md.txt) by comparing performance snapshots. |
| `pg_stat_statements` | Provides a means for tracking execution statistics of all SQL statements executed. |
| `pg_surgery` | Provides functions to perform low-level surgery on relation data. Use this low-level tool with extreme care and as a last resort only. |
| `pg_trgm` | Provides functions and operators for determining the similarity of alphanumeric text based on trigram matching, as well as index operator classes that support fast searching for similar strings. |
| `pg_visibility` | Provides a way to examine the visibility map (VM) and the page-level visibility information of a table. |
| `pg_wait_sampling` | Provides the ability to collect sampling statistics of wait events. > [!IMPORTANT] > **Important:** Before you can use `CREATE EXTENSION` to enable this extension, you must first add the `pg_wait_sampling` extension into [the > `shared_preload_libraries` parameter](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), and you must ensure that the `pg_wait_sampling` extension is loaded by restarting the database. |
| `pgaudit` | Provides detailed session and object audit logging using the standard logging facility provided by PostgreSQL. > [!IMPORTANT] > **Important:** Before you can use `CREATE EXTENSION` to enable this extension, you must first add `pgaudit` into [`shared_preload_libraries`](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), and you must ensure that it's loaded by restarting the database. You must also [set the database flag](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/database-flags.md.txt) `alloydb.enable_pgaudit` to the value `on` in the AlloyDB Omni instance where you want to use the extension. |
| `pgcrypto` | Provides cryptographic functions for PostgreSQL. |
| `pgfincore` | A set of functions to manage pages in operating system disk cache memory from PostgreSQL. |
| `pglogical` | Provides logical streaming replication for PostgreSQL using a publish/subscribe model. AlloyDB Omni includes [a number of plugins](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#logical-plugins) used by the `pglogical` extension. > [!IMPORTANT] > **Important:** Before you can use > `CREATE EXTENSION` to enable this extension, you must first > add `pglogical` into [`shared_preload_libraries`](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/extensions.md.txt#preload-shared-libraries), > and you must ensure that it's loaded by restarting the database. You must also > [set the database flags](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/reference/database-flags.md.txt) > `alloydb.logical_decoding` > to the value `on` in the AlloyDB Omni instance where > you want to use the extension. |
| `pgrowlocks` | Provides row locking information for the specified table. |
| `pgstattuple` | Provides various functions to obtain tuple-level statistics. |
| `pgtap` | Provides a unit testing framework for PostgreSQL, written in PL/pgSQL and PL/SQL. |
| `pgtt` | Adds support for global temporary tables to your databases. |
| `vector` | The stock `pgvector` PostgreSQL extension extension is customized for AlloyDB Omni, and referred to as `vector`. It supports store generated embeddings in a vector column, generate vector-optimized indexes, and search vector embeddings. |
| `plpgsql` | A loadable procedural language for creating functions, procedures and triggers. You also can use this language for direct execution of code in `DO` blocks. |
| `plproxy` | Procedural language handler that allows remote procedure calls among PostgreSQL databases, with optional sharding. |
| `plv8` | Provides a procedural language for enabling JavaScript. |
| `postgres_fdw` | Provides a foreign-data wrapper that you can use to access data stored in external PostgreSQL servers. |
| `postgresql-hll` | Introduces a new data type, `hll`, which is a HyperLogLog data structure. |
| `prefix` | Provides prefix-matching, plus index support. |
| `refint` | Includes functions to check foreign key restraints, the referencing table, and the referenced table. |
| `sslinfo` | Provides information about the SSL certificate that the current client provided when it connected to the instance. |
| `tablefunc` | Provides various functions that return tables (multiple rows). |
| `tcn` | Provides a trigger function that notifies listeners of changes to the content of database tables. |
| `temporal_tables` | Provides support for temporal tables. In databases, a temporal table records the period of time for which a row is valid. |
| `tsm_system_rows` | Provides the table sampling method SYSTEM_ROWS, which can be used in the TABLESAMPLE clause of a SELECT command. |
| `tsm_system_time` | Provides the table sampling method SYSTEM_TIME, which can be used in the TABLESAMPLE clause of a SELECT command. |
| `unaccent` | A text search dictionary that removes accents and other diacritical signs from lexemes. |
| `uuid-ossp` | Provides functions to generate universally unique identifiers (UUIDs) using one of several standard algorithms. |

## Logical decoding plugins

In addition to the extensions listed earlier on this page,
AlloyDB Omni supports the following plugins used by the
`pglogical` extension for formatting that extension's streamed
output.

| Plugin | Description |
|---|---|
| `pgoutput` | PostgreSQL's built-in logical decoding plugin. |
| `test_decoding` | Formats streamed data into a text format. |

## PostGIS extensions

The following [PostGIS extensions](https://www.postgis.net/) are supported, but
are not included in AlloyDB Omni:

- [`postgis`](http://www.postgis.net/)
- [`postgis_raster`](https://postgis.net/docs/RT_reference.html)
- [`postgis_sfcgal`](http://www.sfcgal.org/)
- [`postgis_tiger_geocoder`](http://postgis.net/docs/Geocode.html)
- [`postgis_topology`](http://postgis.net/docs/manual-dev/Topology.html)
- [`address_standardizer`](https://postgis.net/docs/manual-dev/Extras.html)
- [`address_standardizer_data_us`](https://postgis.net/docs/manual-dev/Extras.html)

For more information, see [Install PostGIS for AlloyDB Omni](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/install-postgis.md.txt).

## Orafce extensions

AlloyDB Omni does not include the
[Orafce extension](https://github.com/orafce/orafce), but you can
manually add it to an existing AlloyDB Omni installation by
following the instructions in
[Install Orafce for AlloyDB Omni](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/install-orafce.md.txt)
to provide additional functions and operators from the Oracle database.

## Enable an extension

To enable an extension, follow these steps:

1. [Connect to a database](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/run-connect.md.txt) in AlloyDB Omni
   cluster's primary instance.

2. Run the [`CREATE EXTENSION`](https://www.postgresql.org/docs/16/sql-createextension.html)
   command. For example, after connecting to your primary instance, you can enable
   the `citext` extension using `psql`:

   ```sql
   CREATE EXTENSION IF NOT EXISTS citext;
   ```

## Add extension's shared library to PostgreSQL

To add an extension's shared library to PostgreSQL, you must update the `shared_preload_libraries` database flag in your `DBCluster` manifest.

For detailed instructions on how to do this, see [Update a parameter in AlloyDB Omni on a Kubernetes cluster](https://docs.cloud.google.com/alloydb/omni/containers/16.3.0/docs/configure-database-flags.md.txt#update-parameter-kubernetes-cluster).