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 Instance 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

Glossary

PDF
포커스 모드
폰트 크기
마지막 업데이트 시간: 2024-01-24 11:20:59

A-E
F-J
K-O
P-T
U-Z

A-E

Backup storage It is used to persistently store the underlying storage resources of database data and log backups. Read/write separation It allows the primary instance to perform transaction operations such as insertion, update, and deletion (INSERT, UPDATE, and DELETE) and the secondary instance (read-only) to perform SELECT query operations.

F-J

High reliability It is often used to describe a system that is specifically designed to reduce downtime so as to maintain high availability of its services. Relational database Relational database is a database that is connected and organized based on relational data structure. For a relational database model, the complex data structure is simplified into a binary relation (a two-dimensional table). In a relational database, almost all data operations are performed on one or more relational tables. You can manage the database by sorting, joining, connecting, or selecting those related tables. Common relational databases include Oracle, MySQL, MariaDB, Microsoft SQL Server, Access, DB2, PostgreSQL, Informix, and Sybase, etc.

K-O

Logical backup Logical backup is a process during which data is extracted from a database and stored in a binary file through the SQL language. Logical backup allows you to use software technology to export data from the database and write it to an output file. The format of this file is generally different from that of files in the original database. This file is only an image of the data content in the original database. Therefore, the logical backup file can only be used for logical restoration of the database (i.e., data import) instead of physical restoration according to the original storage characteristics of the database. Logical backup is generally used for incremental backup of data changed after last backup. Cold backup Cold backup is a backup method used when the system is shut down or under maintenance, which means that the data backed up is exactly the same as the data in the system.

P-T

QPS Queries per second (QPS) is a metric for measuring the amount of traffic processed by a particular query server within the specified period of time. Hot backup Hot backup is a backup method used when the system is running normally. In this case, since the data in the system is updated in real time, a lag may occur between the backup data and the real data of the system. Data replication Data is replicated from the primary to the secondary in one of the following methods: strong sync replication, semi-sync replication, or async replication. Database storage Database storage is used to persistently store underlying storage resources of database data and logs. Database admin A database admin (DBA) is a person responsible for managing the database using specialized software to store and organize data. The responsibilities of this role may include capacity planning, installation, configuration, database design, migration, performance monitoring, security, troubleshooting, and backup and restoration. Number of database connections The number of sessions on the client that are connected to the database instance. Database migration As business changes, the database also needs to be migrated from one environment to another along with application businesses, such as from a local IDC to a cloud platform or from a cloud platform to another one. Database instance A database instance is a standalone database environment running in the cloud as the basic data block in TencentDB, which can contain multiple databases created by users and be accessed via the same client tools and applications as those for a standalone database instance. Database engine Database engine is the core service for storing, processing, and protecting data. It allows you to control access permissions and process transactions quickly to meet the requirements of most applications for processing massive amounts of data in corporate scenarios. Database engine is supported by each database instance.

U-Z

Physical backup Physical backup is a backup process in which the operating system files that actually make up the database are copied from one place to another (usually from a disk to a tape). Physical backup is divided into cold backup and hot backup.

도움말 및 지원

문제 해결에 도움이 되었나요?

피드백