[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-08-22。"],[[["\u003cp\u003eAlloyDB Omni 15.7.0 supports a wide range of extensions, all of which are available on every instance, and enabling them typically requires using the \u003ccode\u003eCREATE EXTENSION\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eSeveral extensions, such as \u003ccode\u003eanon\u003c/code\u003e, \u003ccode\u003epg_bigm\u003c/code\u003e, \u003ccode\u003epg_cron\u003c/code\u003e, \u003ccode\u003epg_hint_plan\u003c/code\u003e, \u003ccode\u003epg_squeeze\u003c/code\u003e, \u003ccode\u003epgaudit\u003c/code\u003e, and \u003ccode\u003epglogical\u003c/code\u003e, require adding their shared library to the \u003ccode\u003eshared_preload_libraries\u003c/code\u003e parameter and restarting the database before they can be enabled.\u003c/p\u003e\n"],["\u003cp\u003eCertain extensions like \u003ccode\u003eauto_explain\u003c/code\u003e, \u003ccode\u003egoogle_columnar_engine\u003c/code\u003e, and \u003ccode\u003epg_wait_sampling\u003c/code\u003e necessitate setting specific database flags to \u003ccode\u003eon\u003c/code\u003e before enabling them.\u003c/p\u003e\n"],["\u003cp\u003eAlloyDB Omni supports several logical decoding plugins for use with the \u003ccode\u003epglogical\u003c/code\u003e extension, including \u003ccode\u003edecoderbufs\u003c/code\u003e, \u003ccode\u003epgoutput\u003c/code\u003e, \u003ccode\u003etest-decoding\u003c/code\u003e, and \u003ccode\u003ewal2json\u003c/code\u003e, which are used for formatting streamed output.\u003c/p\u003e\n"],["\u003cp\u003eWhile PostGIS and Orafce extensions are not included in AlloyDB Omni, they can be installed manually by following the instructions provided in the given documentation.\u003c/p\u003e\n"]]],[],null,["# Supported database extensions\n\nSelect a documentation version: 15.7.0keyboard_arrow_down\n\n- [Current (16.8.0)](/alloydb/omni/current/docs/reference/extensions)\n- [16.8.0](/alloydb/omni/16.8.0/docs/reference/extensions)\n- [16.3.0](/alloydb/omni/16.3.0/docs/reference/extensions)\n- [15.12.0](/alloydb/omni/15.12.0/docs/reference/extensions)\n- [15.7.1](/alloydb/omni/15.7.1/docs/reference/extensions)\n- [15.7.0](/alloydb/omni/15.7.0/docs/reference/extensions)\n\n\u003cbr /\u003e\n\nThe following table lists all of the extensions supported by AlloyDB Omni 15.7.0.\n\n\u003cbr /\u003e\n\nAll of these extensions are available on every AlloyDB Omni\ninstance. To enable any of them, see [Enable an extension](#enable).\n| **Note:** Some extensions require additional steps before you can enable them---typically, by [setting one or more database\n| flags](/alloydb/omni/15.7.0/docs/configure-database-flags) on your instances.\n\nLogical decoding plugins\n------------------------\n\nIn addition to the extensions listed earlier on this page,\nAlloyDB Omni supports the following plugins used by the\n`pglogical` extension for formatting that extension's streamed\noutput.\n\nPostGIS extensions\n------------------\n\nThe following [PostGIS extensions](https://www.postgis.net/) are supported, but\nare not included in AlloyDB Omni:\n\n- [`postgis`](http://www.postgis.net/)\n- [`postgis_raster`](https://postgis.net/docs/RT_FAQ.html)\n- [`postgis_sfcgal`](http://www.sfcgal.org/)\n- [`postgis_tiger_geocoder`](http://postgis.net/docs/Geocode.html)\n- [`postgis_topology`](http://postgis.net/docs/manual-dev/Topology.html)\n- [`address_standardizer`](https://postgis.net/docs/manual-dev/Extras.html)\n- [`address_standardizer_data_us`](https://postgis.net/docs/manual-dev/Extras.html)\n\nFor more information, see [Install PostGIS for AlloyDB Omni](/alloydb/omni/15.7.0/docs/install-postgis).\n\nOrafce extensions\n-----------------\n\nAlloyDB Omni does not include the\n[Orafce extension](https://github.com/orafce/orafce), but you can\nmanually add it to an existing AlloyDB Omni installation by\nfollowing the instructions in\n[Install Orafce for AlloyDB Omni](/alloydb/omni/15.7.0/docs/install-orafce)\nto provide additional functions and operators from the Oracle database.\n\nEnable an extension\n-------------------\n\nTo enable an extension, follow these steps:\n\n1. [Connect to a database](/alloydb/omni/15.7.0/docs/run-connect) in AlloyDB Omni\n cluster's primary instance.\n\n2. Run the [`CREATE EXTENSION`](https://www.postgresql.org/docs/current/sql-createextension.html)\n command. For example, after connecting to your primary instance, you can enable\n the `citext` extension using `psql`:\n\n mydatabase=\u003e CREATE EXTENSION IF NOT EXISTS citext;\n\n3. Restart the database to ensure that you can use the extension.\n\nAdd extension's shared library to PostgreSQL\n--------------------------------------------\n\nTo enable an extension, follow these steps:\n\n1. [Connect to a database](/alloydb/omni/15.7.0/docs/run-connect) in AlloyDB Omni\n cluster's primary instance.\n\n2. Run the following command to preload an extension's shared library to PostgreSQL memory. For example, the following command preloads shared libraries of the `pg_stat_statements` extension.\n\n # ALTER SYSTEM SET shared_preload_libraries=pg_stat_statements,pg_stat_statements;\n\n3. Restart the database to ensure that you can use the extension."]]