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

Glossary

Enabling Instance Termination Protection

PDF

フォーカスモード

フォントサイズ

最終更新日: 2026-03-11 16:34:58

Scenarios
Normally, when you no longer need an instance, you can terminate it via the console or API. To prevent accidental termination, you can enable termination protection. Once enabled, the instance cannot be terminated via the console or API. If you have confirmed that the instance needs to be terminated, you can disable termination protection before performing the termination.
By enabling termination protection, you can safeguard instances containing your business data from accidental termination. This document describes how to enable and disable instance termination protection via the console.
Notes
Instance termination protection is disabled by default for both new and existing instances. You can enable it as needed.
Instance termination protection does not take effect for system-level termination. For example, pay-as-you-go instances are terminated due to overdue payments after the instances are shut down, and yearly/monthly subscription instances are terminated upon expiration and after the instances are in the recycle bin for over 7 days.
Operation Steps
Enabling Instance Termination Protection
Enable Termination Protection for Existing Instances
Enabling Termination Protection for New Instances
1. Log in to the TencentDB for PostgreSQL console.
2. You can enable instance termination protection for single or multiple instances based on your needs:
Enable instance termination protection for a single instance:
List View: Locate the instance for which you want to enable termination protection in the instance list. In the Operation column, choose More > Set Instance Termination Protection.
﻿
Tab View: Choose Instance Details > Basic Info > Instance Termination Protection. As shown below:
﻿
Enable termination protection for instances in batches:
On the "Instance List" page, select the instances for which you want to enable termination protection, then choose More > Set Instance Termination Protection at the top of the list. As shown below:
﻿
3. In the pop-up Set Instance Termination Protection window, select Enable, then click OK to enable instance termination protection.
﻿
When purchasing a new instance, select Advanced Configuration > Instance Termination Protection > Prevent instance termination via the console or an API. As shown below:
﻿
Disabling Instance Termination Protection
If you have confirmed that the instance can be terminated, perform the following steps to disable instance termination protection before terminating the instance:
1. Log in to the TencentDB for PostgreSQL console.
2. You can disable termination protection for single or multiple instances based on your needs:
Disable termination protection for a single instance:
List View: Locate the target instance in the instance list. In the Operation column, choose More > Set Instance Termination Protection.
﻿
Tab View: choose Instance Details > Basic Info > Instance Termination Protection. As shown below:
﻿
Batch disable instance termination protection:
On the "Instance List" page, select the instances for which you want to disable termination protection, then choose More > Set Instance Termination Protection at the top of the list. As shown below:
﻿
3. In the pop-up Set Instance Termination Protection window, select Disable, then click OK to disable instance termination protection.
﻿