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 PostgreSQLKernel Version IntroductionProprietary Kernel FeaturesProcess Monitoring

Process Monitoring

PDF
Mode fokus
Ukuran font
Terakhir diperbarui: 2024-03-20 10:32:43

Feature Background

In certain common scenarios, customer applications need not only the overall monitoring information of the database instance, but also need to use the process monitoring information in the instance to judge the business health, and then make business logic decisions. Typically, in SaaS scenarios, a single tenant of the user uses a database of the database instance alone. By monitoring the resource usage of the processes connected to the database, the business party can further judge the current health of the tenant and other situations.

Description of the Feature

TencentDB for PostgreSQL provides process monitoring information for the database instance. The system provides a view named tencentdb_process_system_usage, which contains the following information, as explained below:
Field name
Description
pid
Process Number.
username
Username.
datname
Database Name.
backend_type
Process type. Possible types include autovacuum launcher, autovacuum worker, logical replication launcher, logical replication worker, parallel worker, background writer, client backend, checkpointer, startup, walreceiver, walsender, and walwriter. In addition, backend Workers registered by extensions may have additional types.
query
Refers to the query statement that is being executed currently.
cpu_usage
Refers to the CPU utilization during the current query sampling period. For the sampling interval, the parameter tencentdb_system_stat.sampling_interval is provided for settings. The unit of this parameter is milliseconds and the default value is 1000.
memory_bytes
Refers to the memory usage rate during the current sampling period, in bytes.

Use Instructions

1. Create a new extension with the following command:
postgres => create extension tencentdb_system_stat;
CREATE EXTENSION
postgres =>
2. The usage of the tencentdb_process_system_usage view is the same as other views. You only need to log in to the PostgreSQL database instance and perform a query. Here is an example statement:
select * from tencentdb_process_system_usage;



Topik sebelumnya: Making Buffer Invalid AsynchronouslyTopik selanjutnya: SQL Traffic Throttling

Bantuan dan Dukungan

Apakah halaman ini membantu?

masukan