Postgres extensions
BigAnimal supports many Postgres extensions. See Postgres extensions available by deployment for the complete list.
Installing extensions
Use the CREATE EXTENSION command to install extensions.
You need superuser privileges to install most extensions on BigAnimal. The table in Postgres extensions available by deployment indicates whether an extension requires superuser privileges or not.
Example: Installing multiple extensions
One way of installing multiple extensions simultaneously is to:
Create a text file containing the CREATE EXTENSION command for each of the extensions you want to install. In this example, we've named the file
create_extensions.sql.CREATE EXTENSION <extension_name_1> SCHEMA <schema_name>; CREATE EXTENSION <extension_name_2> SCHEMA <schema_name>; CREATE EXTENSION <extension_name_3> SCHEMA <schema_name>; CREATE EXTENSION <extension_name_4> SCHEMA <schema_name>;
Use your Postgres client of choice to load the extensions. For example, using psql:
psql <biganimal_connection_string> -f create_extensions.sql
For more information about connecting to your cluster using a client, see Connecting to your cluster.
Extensions requiring superuser privileges
Certain extensions require superuser privileges in order to use the extension:
| Extensions requiring superuser to use | Notes |
|---|---|
| amcheck | Can be granted to others |
| pageinspect | |
| pg_buffercache | superuser or pg_monitor role |
| pg_freespacemap | superuser or pg_stat_scan_tables role |
| pgrowlocks | superuser or pg_stat_scan_tables role |
| pgstattuple | superuser or pg_stat_scan_tables role |
| pg_visibility | superuser or pg_stat_scan_tables role |
Working with extensions
Use the DROP EXTENSION command to remove extensions.
Use the pg_available_extensions view to see a list of all PostreSQL extensions.
The catalog_pg_extension catalog stores information about the installed extensions.