tencent cloud

TencentDB for PostgreSQL

Release Notes and Announcements
Release Notes
Product Announcements
Product Introduction
Overview
Features
Strengths
Scenarios
Information Security
Regions and AZs
Product Feature List
Large version lifecycle description
MSSQL Compatible Version
Billing
Billing Overview
Instance Type and Specification
Purchase Methods
Refund
Overdue Payments
Backup Space Billing
Database Audit Billing Overview
Getting Started
Creating TencentDB for PostgreSQL Instance
Connecting to TencentDB for PostgreSQL Instance
Managing TencentDB for PostgreSQL Instance
Importing Data
Migrating Data with DTS
Kernel Version Introduction
Kernel Version Overview
Kernel Version Release Notes
Viewing Kernel Version
Proprietary Kernel Features
Database Audit
Audit Service Description
Activating Audit Service
View Audit Logs
Modify audit services
Audit Performance Description
User Guide
Instance Management
Upgrading Instance
CPU Elastic Scaling
Read-Only Instance
Account Management
Database Management
Parameter Management
Log Management and Analysis
Backup and Restoration
Data Migration
Extension Management
Network Management
Access Management
Data Security
Tenant and Resource Isolation
Security Groups
Monitoring and Alarms
Tag
AI Practice
Using the Tencentdb_ai Plug-In to Call Large Models
Building Ai Applications with the Tencentdb Ai Plug-In
Combining Supabase to Quickly Build Backend Service Based on TencentDB for PostgreSQL
Use Cases
postgres_fdw Extension for Cross-database Access
Automatically Creating Partition in PostgreSQL
Searching in High Numbers of Tags Based on pg_roaringbitmap
Querying People Nearby with One SQL Statement
Configuring TencentDB for PostgreSQL as GitLab's External Data Source
Supporting Tiered Storage Based on cos_fdw Extension
Implement Read/Write Separation via pgpool
Implementing Slow SQL Analysis Using the Auto_explain Plugin
Using pglogical for Logical Replication
Using Debezium to Collect PostgreSQL Data
Set Up a Remote Disaster Recovery Environment for PostgreSQL Locally on CVM
Read-Only Instance and Read-Only Group Practical Tutorial
How to Use SCF for Scheduled Database Operations
Fix Table Bloat
Performance White Paper
Test Methods
Test Results
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Read-only Replica APIs
Backup and Recovery APIs
Parameter Management APIs
Security Group APIs
Performance Optimization APIs
Account APIs
Specification APIs
Network APIs
Data Types
Error Codes
FAQs
Service Agreement
Service Level Agreement
Terms of Service
Glossary
Contact Us
DokumentasiTencentDB for PostgreSQLUser GuideExtension ManagementCreating a Plugin in TencentDB for PostgreSQL Instance

Creating a Plugin in TencentDB for PostgreSQL Instance

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2025-08-14 17:04:48
This document describes how to create a plugin in a TencentDB for PostgreSQL instance.

Prerequisites

The TencentDB for PostgreSQL instance has been created. For specific steps, see Creating TencentDB for PostgreSQL Instance.

Operation Steps

Querying Plugin Support and Supported Versions

Method One: Query Document

The supported plugins and versions vary across different major versions of instances. You can query them in the Overview.

Method Two: Database Query

Log in to the TencentDB for PostgreSQL console and execute the following statement to query supported versions of plugins. This example uses a database instance of major version 17 to create a vector plug-in.
SELECT * FROM pg_available_extensions WHERE name = 'vector';
The returned results are as follows. Among them, the default_version column shows the plugin versions supported for installation. The vector plugin supports version 0.8.0.


2. Modify Parameters (Optional)

Creating some plug-ins requires adding values to the shared_preload_libraries parameter in advance. You can log in to the TencentDB for PostgreSQL console, click Instance ID, then enter the parameter setting webpage, search for the shared_preload_libraries parameter, and click

to modify it.
Note:
**Note:** After editing and saving shared_preload_libraries, the instance will restart to modify parameters. The specific time depends on business conditions. Ensure your application has an automatic reconnection feature.
If the selectable parameter values of shared_preload_libraries do not include the plugin you need to create, but you find the plugin information in Procedure 1, you do not need to modify the parameter value and can directly create the plugin.

Select the plug-in you need and click

to save. In this example, the vector plug-in is not included in the shared_preload_libraries parameter value, so you only need to create it directly.


Creating a Plugin

Log in to the database instance and execute the following statement in the database that requires the use of the plug-in:
CREATE EXTENSION vector;
Note:
Warning: Please try to avoid creating plugins in the postgres system database to avoid potential security risks.
After execution, confirm it by viewing the following statement to check whether creation succeeded.
SELECT * FROM pg_available_extensions WHERE name = 'vector';
The installed_version matches the default_version, indicating the add-on creation was successful.


Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan