dblink_connect — opens a persistent connection to a remote database
dblink_connect_u — opens a persistent connection to a remote database, insecurely
dblink_disconnect — closes a persistent connection to a remote database
dblink — executes a query in a remote database
dblink_exec — executes a command in a remote database
dblink_open — opens a cursor in a remote database
dblink_fetch — returns rows from an open cursor in a remote database
dblink_close — closes a cursor in a remote database
dblink_get_connections — returns the names of all open named dblink connections
dblink_error_message — gets last error message on the named connection
dblink_send_query — sends an async query to a remote database
dblink_is_busy — checks if connection is busy with an async query
dblink_get_notify — retrieve async notifications on a connection
dblink_get_result — gets an async query result
dblink_cancel_query — cancels any active query on the named connection
dblink_get_pkey — returns the positions and field names of a relation's primary key fields
dblink_build_sql_insert — builds an INSERT statement using a local tuple, replacing the primary key field values with alternative supplied values
dblink_build_sql_delete — builds a DELETE statement using supplied values for primary key field values
dblink_build_sql_update — builds an UPDATE statement using a local tuple, replacing the primary key field values with alternative supplied values

F.16. dict_int — example full-text search dictionary for integers

F.16.1. Configuration
F.16.2. Usage

F.17. dict_xsyn — example synonym full-text search dictionary

F.17.1. Configuration
F.17.2. Usage

F.18. earthdistance — calculate great-circle distances

F.18.1. Cube-Based Earth Distances
F.18.2. Point-Based Earth Distances

F.19. fasttrun — function to truncate temporary tables without growing pg_class size

F.19.1. Function
F.19.2. Test example

F.20. file_fdw — access data files in the server's file system

F.21. fulleq — equivalence operator for compatibility with Microsoft SQL Server

F.21.1. Overview
F.21.2. Operator fulleq

F.22. fuzzystrmatch — determine string similarities and distance

F.22.1. Soundex
F.22.2. Daitch-Mokotoff Soundex
F.22.3. Levenshtein
F.22.4. Metaphone
F.22.5. Double Metaphone

F.23. hstore — hstore key/value datatype

F.23.1. hstore External Representation
F.23.2. hstore Operators and Functions
F.23.3. Indexes
F.23.4. Examples
F.23.5. Statistics
F.23.6. Compatibility
F.23.7. Transforms
F.23.8. Authors

F.24. HypoPG — support for hypothetical indexes

F.24.1. Overview
F.24.2. Installation
F.24.3. Updating the extension
F.24.4. Updating the extension
F.24.5. Usage

F.25. intagg — integer aggregator and enumerator

F.25.1. Functions
F.25.2. Sample Uses

F.26. intarray — manipulate arrays of integers

F.26.1. intarray Functions and Operators
F.26.2. Index Support
F.26.3. Example
F.26.4. Benchmark
F.26.5. Authors

F.27. isn — data types for international standard numbers (ISBN, EAN, UPC, etc.)

F.27.1. Data Types
F.27.2. Casts
F.27.3. Functions and Operators
F.27.4. Configuration Parameters
F.27.5. Examples
F.27.6. Bibliography
F.27.7. Author

F.28. lo — manage large objects

F.28.1. Rationale
F.28.2. How to Use It
F.28.3. Limitations
F.28.4. Author

F.29. ltree — hierarchical tree-like data type

F.29.1. Definitions
F.29.2. Operators and Functions
F.29.3. Indexes
F.29.4. Example
F.29.5. Transforms
F.29.6. Authors

F.30. mchar — additional data types for compatibility with Microsoft SQL Server (MS SQL)

F.30.1. Overview
F.30.2. Additional types
F.30.3. MCHAR and MVARCHAR Features

F.31. online_analyze — statistic collection right after INSERT/UPDATE/DELETE/SELECT

F.31.1. Overview
F.31.2. Configuration

F.32. pageinspect — low-level inspection of database pages

F.32.1. General Functions
F.32.2. Heap Functions
F.32.3. B-Tree Functions
F.32.4. BRIN Functions
F.32.5. GIN Functions
F.32.6. GiST Functions
F.32.7. Hash Functions

F.33. page_repair — individual page repair using standby’s data

F.33.1. Overview
F.33.2. Installation
F.33.3. Usage

F.34. passwordcheck — verify password strength

F.34.1. Configuration Parameters

F.35. pgAudit — detailed session and/or object audit logging

F.35.1. Overview
F.35.2. Why pgAudit?
F.35.3. Usage Considerations
F.35.4. Tantor SE-1C Version Compatibility
F.35.5. Settings
F.35.6. Session Audit Logging
F.35.7. Object Audit Logging
F.35.8. Event Marking
F.35.9. Format
F.35.10. Caveats

F.36. pgauditlogtofile — pgAudit addon for redirect audit log lines to an independent file

F.36.1. Overview
F.36.2. Installation
F.36.3. Configuration

F.37. pg_buffercache — inspect Tantor SE-1C buffer cache state

F.37.1. The pg_buffercache View
F.37.2. The pg_buffercache_numa View
F.37.3. The pg_buffercache_summary() Function
F.37.4. The pg_buffercache_usage_counts() Function
F.37.5. The pg_buffercache_evict() Function
F.37.6. The pg_buffercache_evict_relation() Function
F.37.7. The pg_buffercache_evict_all() Function
F.37.8. Sample Output
F.37.9. Authors

F.38. pg_cron — cron-based job scheduler working within the database

F.38.1. Overview?
F.38.2. How pg_cron works
F.38.3. Cron syntax
F.38.4. Managing and creating jobs
F.38.5. Setting up pg_cron
F.38.6. Monitoring jobs

F.39. pgcrypto — cryptographic functions

F.39.1. General Hashing Functions
F.39.2. Password Hashing Functions
F.39.3. PGP Encryption Functions
F.39.4. Raw Encryption Functions
F.39.5. Random-Data Functions
F.39.6. OpenSSL Support Functions
F.39.7. Configuration Parameters
F.39.8. Notes
F.39.9. Author

F.40. pg_csm — estimating compressibility of tables and indexes using CSM

F.40.1. Overview
F.40.2. Installing the extension
F.40.3. Quick start
F.40.4. Configuring compressed storage
F.40.5. smgr_info
F.40.6. csm_compress_analysis
F.40.7. csm_overflow_fork_stat
F.40.8. csm_cache_stat
F.40.9. Notes and limitations

F.41. pg_freespacemap — examine the free space map

F.41.1. Functions
F.41.2. Sample Output
F.41.3. Author

F.42. pg_hint_plan — configuring plans of SQL queries in SQL comments

F.42.1. Overview
F.42.2. Installation
F.42.3. Description
F.42.4. The hint table
F.42.5. Details in hinting
F.42.6. Errors
F.42.7. Functional limitations
F.42.8. Hint list

F.43. pg_logicalinspect — logical decoding components inspection

F.43.1. Functions
F.43.2. Author

F.44. pg_overexplain — allow EXPLAIN to dump even more details

F.44.1. EXPLAIN (DEBUG)
F.44.2. EXPLAIN (RANGE_TABLE)
F.44.3. Author

F.45. pg_prewarm — preload relation data into buffer caches

F.45.1. Functions
F.45.2. Configuration Parameters
F.45.3. Author

F.46. pg_query_id — manipulate aspects of query id computation

F.46.1. Overview
F.46.2. Getting started
F.46.3. Functionality
F.46.4. Known issues

F.47. pg_repack — remove bloat from tables and indexes

F.47.1. Overview
F.47.2. Requirements
F.47.3. Installation
F.47.4. Usage
F.47.5. Environment
F.47.6. Examples
F.47.7. Diagnostics
F.47.8. Restrictions
F.47.9. Details

F.48. pgrowlocks — show a table's row locking information

F.48.1. Overview
F.48.2. Sample Output
F.48.3. Author

F.49. pg_sample_profile — sample-based profiling of database activity

F.49.1. Overview
F.49.2. Usage

F.50. pg_stat_advisor — Tantor SE-1C advisor to create extended statistics

F.50.1. Overview
F.50.2. Limitations
F.50.3. Installation
F.50.4. Usage
F.50.5. Examples

F.51. pg_stat_kcache — statistics about real reads and writes

F.51.1. Overview
F.51.2. Installation
F.51.3. Configuration
F.51.4. Usage
F.51.5. Updating the extension
F.51.6. Bugs and limitations

F.52. pg_stat_statements — track statistics of SQL planning and execution

F.52.1. The pg_stat_statements View
F.52.2. The pg_stat_statements_info View
F.52.3. Functions
F.52.4. Configuration Parameters
F.52.5. Sample Output
F.52.6. Authors

F.53. pgstattuple — obtain tuple-level statistics

F.53.1. Functions
F.53.2. Authors

F.54. pg_store_plans — means for tracking execution plan statistics of all SQL statements

F.54.1. Overview
F.54.2. The pg_store_plans View
F.54.3. The pg_store_plans View
F.54.4. Functions
F.54.5. Configuration Parameters
F.54.6. Discussion on plan_storage setting
F.54.7. Sample Output

F.55. pg_surgery — perform low-level surgery on relation data

F.55.1. Functions
F.55.2. Authors

F.56. pg_trace — Real-time filtered query tracing for Tantor SE-1C

F.56.1. Overview
F.56.2. Getting started
F.56.3. Functionality
F.56.4. Client-Server protocol
F.56.5. Configuration
F.56.6. How it works
F.56.7. Known issues

F.57. pg_trgm — support for similarity of text using trigram matching

F.57.1. Trigram (or Trigraph) Concepts
F.57.2. Functions and Operators
F.57.3. GUC Parameters
F.57.4. Index Support
F.57.5. Text Search Integration
F.57.6. References
F.57.7. Authors

F.58. pg_visibility — visibility map information and utilities

F.58.1. Functions
F.58.2. Author

F.59. pg_wait_sampling — sampling based statistics of wait events

F.59.1. Overview
F.59.2. Installation
F.59.3. Usage

F.60. pg_walinspect — low-level WAL inspection

F.60.1. General Functions
F.60.2. Author

F.61. plantuner — planner hints

F.61.1. Overview
F.61.2. Motivation
F.61.3. Syntax
F.61.4. Usage

F.62. postgres_fdw — access data stored in external Tantor SE-1C servers

F.62.1. FDW Options of postgres_fdw
F.62.2. Functions
F.62.3. Connection Management
F.62.4. Transaction Management
F.62.5. Remote Query Optimization
F.62.6. Remote Query Execution Environment
F.62.7. Cross-Version Compatibility
F.62.8. Wait Events
F.62.9. Configuration Parameters
F.62.10. Examples
F.62.11. Author

F.63. seg — a datatype for line segments or floating point intervals

F.63.1. Rationale
F.63.2. Syntax
F.63.3. Precision
F.63.4. Usage
F.63.5. Notes
F.63.6. Credits

F.64. sepgsql — SELinux-, label-based mandatory access control (MAC) security module

F.64.1. Overview
F.64.2. Installation
F.64.3. Regression Tests
F.64.4. GUC Parameters
F.64.5. Features
F.64.6. Sepgsql Functions
F.64.7. Limitations
F.64.8. External Resources
F.64.9. Author

F.65. sslinfo — obtain client SSL information

F.65.1. Functions Provided
F.65.2. Author

F.66. tablefunc — functions that return tables (crosstab and others)

F.66.1. Functions Provided
F.66.2. Author

F.67. tcn — a trigger function to notify listeners of changes to table content

F.68. test_decoding — SQL-based test/example module for WAL logical decoding

F.69. transp_anon — mask or replace personally identifiable information or commercially sensitive data

F.69.1. Overview
F.69.2. Definitions of the terms used in this project
F.69.3. Anonymization & Data Masking for Tantor SE-1C
F.69.4. Server startup requirement
F.69.5. Configuration
F.69.6. Declare masking rules
F.69.7. Masking functions
F.69.8. Dynamic masking
F.69.9. Generalization
F.69.10. Custom Fake Data
F.69.11. Performances
F.69.12. Security
F.69.13. Examples

F.70. tsm_system_rows — the SYSTEM_ROWS sampling method for TABLESAMPLE

F.70.1. Examples

F.71. tsm_system_time — the SYSTEM_TIME sampling method for TABLESAMPLE

F.71.1. Examples

F.72. unaccent — a text search dictionary which removes diacritics

F.72.1. Configuration
F.72.2. Usage
F.72.3. Functions

F.73. uuid-ossp — a UUID generator

F.73.1. uuid-ossp Functions
F.73.2. Building uuid-ossp
F.73.3. Author

F.74. xml2 — XPath querying and XSLT functionality

F.74.1. Deprecation Notice
F.74.2. Description of Functions
F.74.3. xpath_table
F.74.4. XSLT Functions
F.74.5. Author

This appendix and the next one contain information on the optional components found in the contrib directory of the Tantor SE-1C distribution. These include porting tools, analysis utilities, and plug-in features that are not part of the core PostgreSQL system. They are separate 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 module libraries found in contrib. Appendix G covers utility programs.

Many components supply new user-defined functions, operators, or types, packaged as extensions. To make use of one of these extensions, after you have installed the code you need to register the new SQL objects in the database system. This is done by executing a CREATE EXTENSION command. In a fresh database, you can simply do

CREATE EXTENSION extension_name;

This command registers the new SQL objects in the current database only, so you need to run it in every database in which you want the extension's facilities to be available. Alternatively, run it in database template1 so that the extension will be copied into subsequently-created databases by default.

For all extensions, the CREATE EXTENSION command must be run by a database superuser, unless the extension is considered “trusted”. Trusted extensions can be run by any user who has CREATE privilege on the current database. Extensions that are trusted are identified as such in the sections that follow. Generally, trusted extensions are ones that cannot provide access to outside-the-database functionality.

The following extensions are trusted in a default installation:

btree_gin	fuzzystrmatch	ltree	tcn
btree_gist	hstore	pgcrypto	tsm_system_rows
citext	intarray	pg_trgm	tsm_system_time
cube	isn	seg	unaccent
dict_int	lo	tablefunc	uuid-ossp

Many extensions allow you to install their objects in a schema of your choice. To do that, add SCHEMA schema_name to the CREATE EXTENSION command. By default, the objects will be placed in your current creation target schema, which in turn defaults to public.

Note, however, that some of these components are not “extensions” in this sense, but are loaded into the server in some other way, for instance by way of shared_preload_libraries. See the documentation of each component for details.

Prev	Up	Next
E.6. Prior Releases	Home	F.1. amcheck — tools to verify table and index consistency

Appendix F. Additional Supplied Modules and Extensions

Appendix F. Additional Supplied Modules and Extensions#

Appendix F. Additional Supplied Modules and Extensions

© LLC "Tantor Labs"

Products

Contacts