F. 延伸支援模組
Table of Contents
F.2.2. Usingamcheckeffectively
F.3.1. Configuration Parameters
F.4.1. Configuration Parameters
F.5.3. Operator Class Interface
F.9.3. String Comparison Behavior
— opens a persistent connection to a remote database
— opens a persistent connection to a remote database, insecurely
— closes a persistent connection to a remote database
— executes a query in a remote database
— executes a command in a remote database
— opens a cursor in a remote database
— returns rows from an open cursor in a remote database
— closes a cursor in a remote database
— returns the names of all open named dblink connections
— gets last error message on the named connection
— sends an async query to a remote database
— checks if connection is busy with an async query
— retrieve async notifications on a connection
— gets an async query result
— cancels any active query on the named connection
— returns the positions and field names of a relation's primary key fields
— builds an INSERT statement using a local tuple, replacing the primary key field values with alternative supplied values
— builds a DELETE statement using supplied values for primary key field values
— builds an UPDATE statement using a local tuple, replacing the primary key field values with alternative supplied values
F.14.1. Cube-based Earth Distances
F.14.2. Point-based Earth Distances
F.17.1.hstoreExternal Representation
F.17.2.hstoreOperators and Functions
F.19.1.intarrayFunctions and Operators
F.20.3. Functions and Operators
F.22.2. Operators and Functions
F.26.1. General Hashing Functions
F.26.2. Password Hashing Functions
F.26.3. PGP Encryption Functions
F.26.4. Raw Encryption Functions
F.30.1. Thepg_stat_statementsView
F.30.3. Configuration Parameters
F.32.1. Trigram (or Trigraph) Concepts
F.32.2. Functions and Operators
F.32.5. Text Search Integration
F.34.1. FDW Options of postgres_fdw
F.34.3. Transaction Management
F.34.4. Remote Query Optimization
F.34.5. Remote Query Execution Environment
F.34.6. Cross-Version Compatibility
F.37.1. refint — Functions for Implementing Referential Integrity
F.37.2. timetravel — Functions for Implementing Time Travel
F.37.3. autoinc — Functions for Autoincrementing Fields
F.37.4. insert_username — Functions for Tracking Who Changed a Table
F.37.5. moddatetime — Functions for Tracking Last Modification Time
F.46.2. Description of Functions
This appendix and the next one contain information regarding the modules that can be found in thecontribdirectory of thePostgreSQLdistribution. These include porting tools, analysis utilities, and plug-in features that are not part of the core PostgreSQL system, mainly because they address a limited audience or are too experimental to be part of the main source tree. This does not preclude their usefulness.
This appendix covers extensions and other server plug-in modules found incontrib.Appendix Gcovers utility programs.
When building from the source distribution, these components are not built automatically, unless you build the "world" target (seeStep 2). You can build and install all of them by running:
in thecontribdirectory of a configured source tree; or to build and install just one selected module, do the same in that module's subdirectory. Many of the modules have regression tests, which can be executed by running:
before installation or
once you have aPostgreSQLserver running.
If you are using a pre-packaged version ofPostgreSQL, these modules are typically made available as a separate subpackage, such aspostgresql-contrib.
Many modules supply new user-defined functions, operators, or types. To make use of one of these modules, after you have installed the code you need to register the new SQL objects in the database system. InPostgreSQL9.1 and later, this is done by executing aCREATE EXTENSIONcommand. In a fresh database, you can simply do
This command must be run by a database superuser. This registers the new SQL objects in the current database only, so you need to run this command in each database that you want the module's facilities to be available in. Alternatively, run it in databasetemplate1so that the extension will be copied into subsequently-created databases by default.
Many modules allow you to install their objects in a schema of your choice. To do that, addSCHEMA_schema_name_to theCREATE EXTENSIONcommand. By default, the objects will be placed in your current creation target schema, typicallypublic.
If your database was brought forward by dump and reload from a pre-9.1 version ofPostgreSQL, and you had been using the pre-9.1 version of the module in it, you should instead do
This will update the pre-9.1 objects of the module into a proper_extension_object. Future updates to the module will be managed byALTER EXTENSION. For more information about extension updates, seeSection 37.15.
Note, however, that some of these modules are not“extensions”in this sense, but are loaded into the server in some other way, for instance by way ofshared_preload_libraries. See the documentation of each module for details.
Last updated
Was this helpful?