---
title: "Cloud DB for PostgreSQL prerequisites"
slug: "clouddbforpostgresql-spec"
updated: 2026-09-17T09:25:07Z
published: 2026-09-17T09:25:07Z
canonical: "guide.ncloud-docs.com/clouddbforpostgresql-spec"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud DB for PostgreSQL prerequisites

Available in VPC

View supported environments, server specifications, service limits, etc., for best usage of Cloud DB for PostgreSQL.

## Cloud environment specifications

Cloud environment specifications supported by Cloud DB for PostgreSQL are described as follows:

| Item | Specifications |
| --- | --- |
| Region (zone) | Korea, Singapore, and Japan |
| Classic | Not supported |
| VPC | Supported |
| Languages | Korean, English, and Japanese |

## Server specifications

For NAVER Cloud Platform's Cloud DB for PostgreSQL, you can flexibly select from various types of server type and use them according to your service size. For server specifications supported by Cloud DB for PostgreSQL, see [**Services > Database > Cloud DB for PostgreSQL**](https://www.ncloud.com/product/database/cloudDbPostgresql) in the portal.

### Service limits when changing server specifications

The type of an operational PostgreSQL Server that has been created and is in operation cannot be changed, but the available memory size can be changed at any time using the **change specifications** feature in the console **DB Server** menu. For the upgrade method, see [DB Server](/docs/en/clouddbforpostgresql-postgresqlserver#db-server-%EC%8A%A4%ED%8E%99-%EB%B3%80%EA%B2%BD). However, a few service limits exist when changing the server specifications. You need to fully understand these restrictions before changing the server specifications. The service limits are as follows:

- They can only be changed within the same type.
- If configured with more than 2 servers (using high availability and using Read Replica), change all to the same specification.
- The server restarts upon completion of the change. Therefore, the service may possibly be affected.

## Server redundancy configuration

Cloud DB for PostgreSQL supports the high availability (HA) feature. If a failure occurs on the active server (Primary) and normal service is not available, the system automatically Failover to the standby server (Secondary). Because access is available via DNS, no application changes are required. When creating PostgreSQL Server in the NAVER Cloud Platform console, you can choose whether to use high availability (HA) or not, and the server configuration depends on whether to use it.

              Caution

              

Failover may take a certain amount of time (minutes).

## Pricing information

Cloud DB for PostgreSQL uses a pay-as-you-go pricing plan. For detailed description of Cloud DB for PostgreSQL's pricing standard, see **Portal > Services > Database > Cloud DB for PostgreSQL**.

- [**Portal > Service > Database > Cloud DB for PostgreSQL**](https://www.ncloud.com/product/database/cloudDbPostgresql)