Yandex.Cloud
  • Services
  • Why Yandex.Cloud
  • Solutions
  • Pricing
  • Documentation
  • Contact us
Get started
Yandex Managed Service for PostgreSQL
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Information about existing clusters
    • Creating clusters
    • Connecting to databases
    • Stop and start the cluster
    • SQL queries in the management console
    • Changing cluster and database settings
    • Connecting to DataLens
    • Managing PostgreSQL hosts
    • Database management
    • How to manage PostgreSQL extensions
    • Managing database users
    • Granting permissions and roles
    • Managing backups
    • Deleting clusters
    • Database migration to the Cloud
    • Creating a logical replica of Amazon RDS for PostgreSQL in Managed Service for PostgreSQL
  • Solutions
    • Creating a PostgreSQL cluster for 1C
  • Concepts
    • Relationship between service resources
    • Host classes
    • Network in Yandex Managed Service for PostgreSQL
    • Quotas and limits
    • Storage types
    • Backups
    • Assigning roles
    • Replication
    • Supported clients
  • Access management
  • Pricing policy
    • Current pricing policy
    • Archive
      • Before January 1, 2019
      • From January 1 to March 1, 2019
      • From March 1, 2019 to February 1, 2020
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • BackupService
      • ClusterService
      • DatabaseService
      • ResourcePresetService
      • UserService
      • OperationService
    • REST
      • Overview
      • Backup
        • Overview
        • get
        • list
      • Cluster
        • Overview
        • addHosts
        • backup
        • create
        • delete
        • deleteHosts
        • get
        • list
        • listBackups
        • listHosts
        • listLogs
        • listOperations
        • move
        • rescheduleMaintenance
        • restore
        • start
        • startFailover
        • stop
        • streamLogs
        • update
        • updateHosts
      • Database
        • Overview
        • create
        • delete
        • get
        • list
        • update
      • ResourcePreset
        • Overview
        • get
        • list
      • User
        • Overview
        • create
        • delete
        • get
        • grantPermission
        • list
        • revokePermission
        • update
      • Operation
        • Overview
        • get
  • Questions and answers
    • General questions
    • Questions about PostgreSQL
    • All questions on the same page
  1. Step-by-step instructions
  2. How to manage PostgreSQL extensions

Managing PostgreSQL extensions

  • How to get a list of extensions
  • How to change a set of extensions
  • Supported extensions PostgreSQL

Managed Service for PostgreSQL supports many standard and some non-standard PostgreSQL extensions. A full list of available extensions is given below.

How to get a list of extensions

CLI
API

If you don't have the Yandex.Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To get a list of extensions for a specific database, run the command:

$ yc managed-postgresql database get <database name> \
     --cluster-name <cluster name>

The enabled extensions will be listed in the extensions list.

To get a list of extensions for the cluster database, use the get method.

How to change a set of extensions

CLI
API

If you don't have the Yandex.Cloud command line interface yet, install and initialize it.

The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name or --folder-id parameter.

To enable or disable PostgreSQL extensions for a database, pass the full list of the required extensions in a CLI command. The enabled extensions that aren't in that list will be disabled.

$ yc managed-postgresql database update <database name> \
     --cluster-name <cluster name>
     --extensions <extension name>=<version>,<extension name>=<version>...

Note

The extension version is not considered when handling the command: you can pass any non-empty string as a version.

To pass a new list of DB extensions, use the update method.

Supported extensions PostgreSQL

All supported extensions are listed here:

  • address_standardizer
  • address_standardizer_data_us
  • autoinc
  • bloom
  • btree_gin
  • btree_gist
  • chkpass
  • citext
  • cube
  • dblink (requires the owner or mdb_admin role).
  • dict_int
  • dict_xsyn
  • earthdistance
  • fuzzystrmatch
  • hstore
  • intarray
  • isn
  • jsquery
  • lo
  • ltree
  • moddatetime
  • pg_partman
  • pg_repack (requires the owner or mdb_admin role).
  • pg_stat_kcache (some functions require the owner or mdb_admin role).
  • pg_stat_statements
  • pg_trgm
  • pgcrypto
  • pgrouting
  • pgrowlocks
  • postgis
  • postgis_tiger_geocoder
  • postgis_topology
  • postgres_fdw (requires theowner or mdb_admin role).
  • seg
  • tablefunc
  • unaccent
  • uuid-ossp
  • xml2
In this article:
  • How to get a list of extensions
  • How to change a set of extensions
  • Supported extensions PostgreSQL
Language / Region
Careers
Privacy policy
Terms of use
Brandbook
© 2021 Yandex.Cloud LLC