DB Server

Available in VPC

In DB Server, you can create or delete Cloud PostgreSQL Servers, as well as check the list of Cloud PostgreSQL Servers in operation. In addition, you can change the specifications for the PostgreSQL Servers in operation, or manage admin (user) accounts.

DB Server interface

The basic description of using DB Server is as follows:

Check PostgreSQL Server list

You can check the information of each server from the list of PostgreSQL Servers that have been created and are in operation. To view the information:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for PostgreSQL.

2. Click the DB Server menu.

3. If the list of the created PostgreSQL Servers appears, check the summary information or click PostgreSQL Server to check the details.
   

   • DB Service name: Service name of PostgreSQL, a group that classifies PostgreSQL Server by role. Generally refers to a server group that consists of 1 Primary Server, 1 Secondary Server, and multiple Read Replica Server. PostgreSQL Servers with the same data are referred to as 1 Service.
     • : Click to change the service name.
   • DB Role: Roles of PostgreSQL Server
   • DB Server name: Name of PostgreSQL Server
   • DB Server type: Type of PostgreSQL Server and its available memory
   • Monitoring: Go to the monitoring screen.
   • DB Status: Directs to the view DB Server details page.
   • DB access port: Port number being used by PostgreSQL Server
   • Multi Zone: Whether Multi Zone is being used (Y or N).
   • Private domain: Information of the private domain.
   • Data storage: Size of the data storage in use (available capacity).
   • Data storage type: Type of data storage in use.
   • Data storage capacity: available capacity and used capacity of the data storage in use.
   • Apply data storage encryption: Whether encryption is enabled for saving to the data storage (Y or N).
   • Status: Status of PostgreSQL Server
     • Creating: Status in which PostgreSQL Server is being created with the information entered by the user
     • Configuring: Status in which PostgreSQL Server is being configured after being created with the information entered by you.
     • Running: Status in which the creation and configuration of PostgreSQL Server has been completed with the information entered by user, and access to the PostgreSQL from the application server is available
     • Deleting: Status in which PostgreSQL Server created is being deleted with the information entered by the user
     • Stopping: Status in which PostgreSQL Server created is being stopped with the information entered by the user
     • Restarting: Status in which PostgreSQL Server created is being restarted with the information entered by the user
     • Starting: Status in which PostgreSQL Server specs are being started with the specs selected by the user
     • Upgrading: Status in which PostgreSQL Server specs are being upgraded with the specs selected by the user
     • Downgrading: Status in which PostgreSQL Server specs are being downgraded with the specs selected by the user
     • Failover pending: Status in which failover is required while the user is performing an OS upgrade.
   • Created date: Date when PostgreSQL Server was created, the initial point when the server entered Creating status
   • Running date: Date when PostgreSQL Server started running, the initial point when the server entered Running status
   • ACG: ACG name and ID used in PostgreSQL Server
     • : Click to move to Server > ACG.
     • [View rules]: Click to view the detailed rules applied.
   • Database Config: Config applied to PostgreSQL Server.
     • : Click to go to the Database Config page.
   • DB engine version: Information of the PostgreSQL version installed on the Server
   • DB License: License information of the PostgreSQL installed on the server
   • VPC: VPC name being used in PostgreSQL Server.
   • Server generation: Generation of the server where PostgreSQL Server is installed.
   • Subnet: Name of the Subnet being used by PostgreSQL Server.
   • Private IP: Private IP information applied to PostgreSQL Server.
   • High availability: Whether the high availability feature is enabled (Y or N).
   • Backup storage period (backup time): The configured backup file storage period and backup cycle, if the backup feature is enabled.
     • : Click to set backup options, file storage period, number of stored files, and backup compression.

Create PostgreSQL Server

To create PostgreSQL Server on the NAVER Cloud Platform console:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for PostgreSQL.

2. Click the DB Server menu.

3. Click [Create DB Server].
   

4. When the service subscription page appears, take the following steps in order:

   • 1. Set server
   • 2. Set DB
   • 3. Final confirmation

1. Set server

To create a server to install PostgreSQL by entering the settings:

1. When the Set server page appears, check the type of DBMS you want to install to the server from DBMS type.
   

2. Check the version and license information of the Server PostgreSQL to be installed.

   • Server generation: Server generation information supported in NAVER Cloud Platform information.
   • DB engine version: PostgreSQL version information that can be created in NAVER Cloud Platform
   • DB license: Open source license information of PostgreSQL that can be created in NAVER Cloud Platform.

3. Set additional options for the availability of the server to be created.

   • Support high availability: Click to select whether to use the failover feature for automatic recovery in case of failure.
     • Configure redundancy with two PostgreSQL Servers, a Primary Server and a Secondary Server if you select.
     • When selected, set backup file retention period and backup time (default: 1 day, automatic).
     • When selected, disabling the storage of backup files is not possible.
     • When selected, additional fees will be incurred.
     • The Secondary Server is not accessible by individual users.
   • Multi Zone: To secure advanced high availability, click to select whether to create a Primary Server and a Secondary Server separately in 2 different zones (1 in each zone).

4. Set items related to VPC and PostgreSQL Server, which are needed for the creation of PostgreSQL Server.

   • VPC: Select a VPC to be used for creating a server and PostgreSQL.
     • [Refresh]: Click to view the latest version of the VPC list.
     • [Create VPC]: Click if you haven't created any VPC and need to create one.
   • Subnet: Select a private subnet to be used when accessing VPC.
     • [Refresh]: Click if you want to see the latest version of the created subnet list
     • [Create Subnet]: Click if you haven't created any Subnet and need to create one.
   • DB Server type: Select the PostgreSQL type to be created and available memory according to the server type.
   • Apply data storage encryption: Click to select the usage status of encryption when saving DB data to storage.
     • The settings can't be changed after the creation of the PostgreSQL Server.
   • Data storage type: Click to select the storage type for saving DB data, between SSD and HDD.
     • The settings can't be changed after the creation of the PostgreSQL Server.
   • Data storage capacity: View the storage capacity for saving DB data.
     • 10 GB is assigned upon initial creation of the PostgreSQL Server.
     • The capacity is automatically added in 10 GB units and charged as data increases.
     • Supports up to 6000 GB.

5. Check the applicable pricing plan information when using Cloud DB for PostgreSQL.

   • Pricing plan: An hourly pricing plan, which is billed based on the hours used, is applied by default, and it is changed depending on the server specifications and storage capacity.
   • For more information, click Pricing information.

6. Set the rest of the items required for the creation of the PostgreSQL Server.

   • DB Server name: Enter the name of the PostgreSQL Server to be created.
     • Enter between 3 and 20 characters using lowercase English letters, numbers, and hyphens (-).
     • It must start with an English letter and end with an English letter or a number.
     • To identify servers, random text and a 3-digit number are assigned automatically after the name that was entered by the user. Example: mypostgresql-001-xxxx.
     • Duplicate names are not allowed.
   • DB Service name: Enter the group name that classifies PostgreSQL Servers to be created by its role. Example: mypostgresql-service.
     • Enter between 3 and 30 characters using Korean letters, English letters, numbers, and hyphens (-).
     • Duplicate names are not allowed.
   • Set ACG: Access Control Group (ACG) is created automatically.
     • The detailed settings for the ACG are available from Server > ACG in the console.

7. Click [Next].

2. Set DB

To set the information for the PostgreSQL to be installed:

1. When the Set DB page appears, set items needed for the creation of the PostgreSQL Server.
   

   • USER_ID: Enter the account ID of PostgreSQL Server admin.
     • Enter between 4 to 16 characters using English letters, numbers, and special characters (_).
     • The first character must be an English letter.
     • You cannot use predefined reserved words.
   • Access control: Enter the client’s CIDR that allows you to access the PostgreSQL Server
     • When access is allowed for all. Example: 0.0.0.0/0
     • When allowing access of only a specific IP. Example: 123.123.123.123/32
     • When allowing access of only a specific IP range. Example: 123.123.123.0/24
   • USER password: Enter the account password of the PostgreSQL Server admin.
     • Enter between 8 to 20 characters containing at least one English lowercase letter, number, and special character (_).
     • The special characters ` & + \ " ' / or spaces can't be used.
   • DB access port: Enter 5432 or between 10000 to 20000 as a TCP port number to allow access to the PostgreSQL server that will be created
     • Default: 5432.
     • The port number can't be changed after it is specified.
   • Default DB name: Enter the name of the DB to be created by default.
     • Enter between 1 and 30 characters using English letters, numbers, and special characters (_).
     • The first character must be an English letter.
   • DB Config settings: View the optimized basic settings provided by NAVER.
     • View details > you can view and change the content from DB Config.
   • Collect DB log: View the provision of log collection and viewer features for error logs and slow query logs.
     • Cloud Log Analytics integrations.

2. Set whether to use backup for the server.

   • Backup settings: Set whether to use the backup, backup file retention period, and backup time.
     • Use the Backup settings for the PostgreSQL Server.: Click and select to use for backup.
     • Backup file retention period: Click and select the period to store the backup file in a separate backup storage.
       • For point-in-time recovery, the backup file is stored for the maximum set retention period + 24 hours.
     • Number of backup files to retain: Sets the maximum number of backup files to retain when backup is enabled.
       • You can set up to 30 backup files to be retained.
     • Backup compression: Select whether to compress backup files when backup is enabled.
     • Backup time: Select the backup time between automatic and user-defined.
     • If you select this, additional fees will be incurred depending on the storage capacity used.
       • Automatic: Backup is automatically started every day.
       • User-defined: Backup is started every day within +15 minutes from the time you selected.

3. Click [Next].

4. When the Request subscription to Cloud Log Analytics appears, view the content, and click [OK].

   • If you need to subscribe to Cloud Log Analytics, click [Subscribe to Cloud Log Analytics].
   • For more information about Cloud Log Analytics, see Cloud Log Analytics user guide.

3. Final confirmation

1. When the final confirmation page appears, check the configured server information, DB information, and backup information.
   
   • Click [Previous] to edit the settings.
2. Click [Create].
3. Check the status of the PostgreSQL that was created from the PostgreSQL list on the DB Server page.
   • Creating: Status in which the PostgreSQL Server is being created with the information entered by the user.
   • Configuring: Status in which the PostgreSQL Server is being configured after being created with the information entered by the user.
   • Operating: Status in which the creation and configuration of the PostgreSQL Server has been completed with the information entered by user, and access to PostgreSQL from the application servers is available.

Restart PostgreSQL Server

You can easily and conveniently restart PostgreSQL Servers. You can't access servers while they're being restarted. To restart:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for PostgreSQL.
2. Click the DB Server menu.
3. Click the PostgreSQL Server you want to restart and click [Restart DB Server].
4. When the Restart DB Server popup window appears, check the name of the DB Server to restart, and click [OK].
5. Check the status of the PostgreSQL Server that was created from the PostgreSQL Server list on the DB Server page.
   • Stopping: Status in stopping the operation of PostgreSQL Server
   • Restarting: Status in which the PostgreSQL Server is being restarted.

Delete PostgreSQL Server

You can delete the PostgreSQL Server that has been created and is in operation. If you're using high availability, then both Primary Server and Secondary Server will be deleted. If you're using the backup feature, then the backup files are also deleted. To delete:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for PostgreSQL.
2. Click the DB Server menu.
3. Click PostgreSQL Server you want to delete, and click [Delete DB Server].
4. When the Delete DB Server popup window appears, enter the name of the DB Server to delete, and then click [OK].
5. Check the status of the PostgreSQL Server that was created from the PostgreSQL Server list on the DB Server page.
   • Deleting: Status in which PostgreSQL Server is being deleted.

PostgreSQL Server monitoring

NAVER Cloud Platform's Cloud DB for PostgreSQL provides a monitoring service through the dashboards on each server. This allows users to intuitively check servers in operation and data status and efficiently manage them.

To go to the monitoring page of the PostgreSQL Server that has been created and is in operation:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for PostgreSQL.
2. Click the DB Server menu.
3. Click PostgreSQL Server you want to monitor, and click [Monitoring].
4. Click and select the dashboard you want to monitor.
   

Manage PostgreSQL Server

While operating the created PostgreSQL Server, situations where you need to change the options related to the server or DB set upon creation may occur. Cloud DB for PostgreSQL supports change or upgrade of a certain number of specifications simply through a few clicks, even for PostgreSQL Servers that have already been created.

To manage the PostgreSQL Server that has been created and is in operation:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for PostgreSQL.
2. Click the DB Server menu.
3. Click the PostgreSQL Server you want to manage, and click [Manage].
4. Click and select the item you want to manage.
   
   • View DB Service details
   • View DB Server details
   • Add Read Replica
   • Change high availability settings
   • Change DB Server specifications
   • Manage DB Config
   • Manage public domain
   • Manage DB user
   • DB User permissions management
   • Change DB Server Log settings
   • DB Failover
   • Version Upgrade
   • Manage schema
   • How to access DB Server
   • Manage operation system
   • Change return protection settings

View DB Service details

You can view or edit details related to Database, Config, User, and Backup for the selected PostgreSQL service. The details are as follows:

To view or edit the details:

1. When the View DB Service details page appears, select the Manage Database tab menu.
2. View the database information, and add, edit, or delete databases.
   
   • Add: Enter the database name to be added to Database name, select the user to manage the database from Owner, and click [Add database].
   • Delete: Click [Delete] in the Settings field of the database to be deleted.
3. Click [Save].
4. Click the Manage DB config tab menu.
5. View the DB Config information, and add, edit, or delete Config.
   
   • How to add, edit, or delete: See Manage DB config.
6. Click [Save].
7. Click the Manage DB User tab menu.
8. View the DB User information, and add, edit, or delete User.
   
   • How to add, edit, or delete: See Manage DB User.
9. Click [Save].
10. Click the DB User permissions management tab menu.
11. View the DB User privileges information and add or delete privileges.
    
    • How to add or delete: See DB User permissions management.
12. Click [Save].
13. Click the Manage Backup settings tab menu.
14. View the Backup settings information and adjust settings for required items.
    
    • Backup file retention period: Maximum retention period for the backup files when using the backup feature
    • Backup time: Backup execution time when using the backup feature
15. Click [Save].
16. Click the Manage extensions tab menu.
17. View the Extension information, and add, set, or delete Extensions.
    
    • For more details on how to add, edit, or delete: Refer to Manage Extension.
18. Click [Save].
19. Click the **Manage Public Schema ** tab menu.
20. You may grant or retrieve the Public Schema permission in Database.
    
21. Click [Save].

View DB Server details

You can check the details related to the server to see if the selected PostgreSQL Server is running properly. The details are as follows:

To view the information:

1. When the view DB Server details page appears, click the pg_stat_activity tab menu.
2. View the statistics information for the session process currently in use in the selected PostgreSQL Server, and run necessary commands.
   • Forcibly stop the session: Click terminate.
   • Stop SQL from running: Click cancel.
   • Display SQL extracted: Click sql.
3. Click the pg_settings tab menu.
4. Check the runtime parameter information for the selected PostgreSQL Server.
   
5. Click the pg_stat* tab menu.
6. View the statistics information related to the selected PostgreSQL Server.
   
7. Click the DB Server Logs tab menu.
8. View the selected PostgreSQL Server’s log file information and run necessary commands.
   
   • Save log file to storage: Click [Send to Object Storage] to select a bucket to save and click [Send to Object Storage].
     • If a subscription request to Object Storage hasn't been made: Click [Go to the Object Storage product] to request a subscription and create 1 or more buckets.
   • Delete log file: Click [Delete Log].

Add Read Replica

You can create read-only replica servers for the selected PostgreSQL Server (Primary Server). Up to 5 Read Replica DB in each Zone per server can be created. You can also set up load balancing for database read load by using Read Replica DB Servers through Load Balancer of NAVER Cloud Platform. For more information about how to set it up, see Set read load balancing.

The settings of Read Replica PostgreSQL Server are applied identically to Primary PostgreSQL Server.

• DB Server type
• Data storage type
• Data storage capacity
• DB Config settings

The same fees apply for Read Replica PostgreSQL Server as Primary PostgreSQL Server, and the fees are charged based on the hours used. To add a Read Replica PostgreSQL Server:

1. When the Read Replica popup window appears, check the information for Primary Server DB Server and Read Replica DB Server.
   
2. Click [Yes].
3. Check the status of the Read Replica PostgreSQL Server created from the PostgreSQL list in the DB Server page.
   • Creating: Status in which the Read Replica PostgreSQL Server is being created with the information entered by the user.
   • Configuring: Status in which the Read Replica PostgreSQL Server is being configured after being created with the information entered by the user.
   • Operating: Status in which the creation and configuration of the Read Replica PostgreSQL Server has been completed with the information entered by user, and access to Read Replica PostgreSQL from the application servers is available.

Set read load balancing

You can set up read load balancing for database read load by using Read Replica DB Servers as read-only replica through Load Balancer of NAVER Cloud Platform. First, create a Load Balancer, and then add settings to the PostgreSQL Server's ACG to allow proper access of the created load balancer. To configure settings:

1. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Networking > Load Balancer.
2. Click [Create Load Balancer].
3. Enter the information required for the creation of the Load Balancer and listener.
4. Click [Create Load Balancer].
5. In the VPC environment of the NAVER Cloud Platform console, navigate to Menu > Services > Database > Cloud DB for PostgreSQL.
6. Click the DB Server menu.
7. From the details page of the server to be configured, click of the ACG.
8. Click [Set ACG].
9. Add settings to allow the access for the Load Balancer.
   • Protocol: TCP
   • Access source: IP address range of the Load Balancer subnet
   • Allowed port: DB Server port
10. Click [Apply].
11. On the VPC environment of the NAVER Cloud Platform console, check the creation result from Menu > Services > Networking > Load Balancer menu.
    • Access information: Used when checking the IP for Load Balancer access and accessing for read balancing.
    • Applied server: Check if the connection status of the applied server is displayed as succeeded.

Change high availability settings

You can change the selected PostgreSQL Server to have Standalone or high availability configuration. To change:

1. When the Change high availability settings popup window appears, view the basic server information.
   
2. If the existing high availability setting is Y, it may be set to Standalone; if the existing high availability setting is N, it may be set to high availability.
   • If changing to a high availability configuration, click and select whether to use a Multi Zone.
     When selected, 1 Primary DB and 1 Secondary DB are created in different zones to provide higher availability.
3. Click [OK].
4. Check the status of the PostgreSQL Server from the PostgreSQL Server list on the DB Server page.
   • Configuring: Status in which PostgreSQL Server is being configured after being created with the information entered by you.
   • Running: Status in which the creation and configuration of PostgreSQL Server has been completed with the information entered by user, and access to the PostgreSQL from the application server is available.

Change DB Server specifications.

You can change the server specifications for the PostgreSQL Server you created. Additional fees are incurred for upgrading specifications.

To change the specifications:

1. When the Change specifications popup window appears, check the current server specifications.
2. Click and select the server specifications you want to change to.
   
3. Click [Yes].
4. Check the status of PostgreSQL for which you changed specifications from PostgreSQL list in DB Server page.
   • Configuring: Status in which PostgreSQL server is being configured with the information entered by the user.
   • Operating: Status in which the configuration of PostgreSQL Server has been completed with the information entered by user, and access to PostgreSQL from the application servers is available.

Manage DB Config

You can change various settings for the created PostgreSQL Server. Changes made will apply to all services, and changes made to some Config cause the server to automatically restart before application. To change:

1. When the Database config popup window appears, view or enter the required information for editing.
   
   • Config Name: Name of the config variable
   • Config Value: Variable value
   Note

   For more information on config variables, see PostgreSQL official document.

2. Click [Add].
   • When editing the added config variable, click [Edit].
   • When deleting the added config variable (setting it to default), click [Delete].
3. Click [Save].
4. Check the status of the PostgreSQL for which you changed Config from the PostgreSQL list in the DB Server page.
   • Configuring: Status in which PostgreSQL server is being configured with the information entered by the user.
   • Operating: Status in which the configuration of PostgreSQL Server has been completed with the information entered by user, and access to PostgreSQL from the application servers is available.

Manage public domain

You can request a public domain to allow access to the PostgreSQL Server from outside of NAVER Cloud or remove the configured public domain. Upon configuring a public domain, the data communicated from the outside is charged based on network usage. To request and cancel:

1. When the Request Public domain popup window appears, check the name of the DB Server to request the public domain.
   
2. Click [Yes].

Manage DB user

When creating a PostgreSQL Server, the ID and password for the account that will use the server are created by default. However, while operating the server, you may need to add users or reset the passwords of existing user accounts. You may also need to delete user accounts. Cloud DB for PostgreSQL provides an User management feature that enables you to conveniently add, edit, and delete user accounts that use the server. The results of the user account change through the User management feature are applied to the entire service. Up to 1000 user accounts can be added.

To add or delete user accounts or change the password of the existing admin account:

1. When the Manage DB user popup window appears, perform the required tasks for the user account.
   
   • Add user account: Enter the information for USER_ID, access control, and password, click and select a Replication role, and click [Add DB User].
   • Delete user account: Click [Delete] in the same row as the user account to be deleted.
   • Edit user account password: Click [Edit] in the same row as the user account to be edited, and click [Save] after editing.
2. Click [OK].
3. Check the status of the PostgreSQL for which you've set users from the PostgreSQL list in the DB Server page.
   • Configuring: Status in which PostgreSQL server is being configured with the information entered by the user.
   • Operating: Status in which the configuration of PostgreSQL Server has been completed with the information entered by user, and access to PostgreSQL from the application servers is available.

DB User permissions management

PostgreSQL allows for predefined sets of privileges that can be granted to specific users as needed. Cloud DB for PostgreSQL ensures system stability by internally safeguarding superuser privileges. Although superuser privileges are not granted directly to you, certain predefined roles, which can only be granted or revoked by a superuser, can be controlled. Additionally, select privileges on certain views accessible only by superusers can also be granted or revoked. However, it is recommended to adhere to the principle of least privilege and grant only the minimum necessary privileges.

To add or delete privileges for a user account:

1. Navigate to DB Management > View DB Service Details > DB User permissions management tab.
2. Check the USER_ID and select the privileges to grant or revoke under Privileges.
3. Click [Save].
   

Change DB Server log settings

You can change the log storage settings for the PostgreSQL Server you created. The changes made will be applied to all services. To change:

1. When the Change DB Server Log settings popup window appears, proceed with the tasks necessary for changing the settings.
   
   • Log: View server log name
   • Log Rotation Age: Click and select the log storage cycle (time) (default: 24 hours)
   • Log Rotation Size: Click and select the log storage cycle (capacity) (default: 10 MB)
   • Log Archive Count: Click and select the log storage cycle (number of logs) (default: 100 logs)
2. Click [Save].
3. Check the status of PostgreSQL for which you've set server logs from PostgreSQL Server list on DB Server page.
   • Configuring: Status in which PostgreSQL server is being configured with the information entered by the user.
   • Operating: Status in which the configuration of PostgreSQL Server has been completed with the information entered by user, and access to PostgreSQL from the application servers is available.

DB Failover

If the Primary PostgreSQL Server fails, then the user can directly use the Failover feature to switch between the Primary and Secondary. The switch takes a certain amount of time (minutes) and the server access is unavailable during the switch. To switch:

1. When the DB Failover popup window appears, check the displayed information.
   
2. Click [Yes].

Version Upgrade

You can upgrade the version of the PostgreSQL engine. Two upgrade methods are provided: Minor Version Upgrade and Major Version Upgrade.

1. Click DB management > version upgrade.
2. The PostgreSQL DB Engine Version Upgrade popup window appears.

Minor Version Upgrade

Upgrades the minor version within the same major version. The upgrade is applied to the entire DB service and proceeds sequentially, one server at a time, in the following order: Read Replicas → Secondary → DB Failover → Prior Primary. The operation takes approximately 1 minute per server, and access to the server being upgraded is blocked during the upgrade.

1. Click DB Management > Version Upgrade.
2. The PostgreSQL DB Engine Version Upgrade popup window appears.
3. Leave the Major version upgrade checkbox unchecked.
4. Select the minor version to upgrade to from the DB engine version list.
5. Click [OK].

Major Version Upgrade

Upgrades the PostgreSQL major version. This process uses a pre-built migration method: a new cluster is created while the existing cluster is retained, data is synchronized, and then pg_upgrade is executed.

Major Version Upgrade Overview

The Major Version Upgrade proceeds in the following order:

1. Create a new cluster: A new cluster is created with the same configuration as all servers included in the target server list. The number of servers created matches the number of servers in the existing cluster.
2. Data synchronization: After the new cluster is created, it is connected to the existing cluster via physical replication to synchronize data.
3. Upgrade standby: Once synchronization is complete, the Major Version Upgrade feature is enabled in the DB engine version section of the console. At this stage, pre-access testing is possible in a read-only state.
4. Run pg_upgrade: You can execute pg_upgrade on the new cluster using the Major Version Upgrade button.
5. Access restriction: Access to the new cluster is restricted until pg_upgrade is completed.

Step 1. Start migration

1. Select the Major version upgrade checkbox.
2. Configure or verify the following items:
   • Server generation: Same server generation as the existing cluster
   • DB Server name: DB Server name for the new cluster
   • DB Service name: DB Service name for the new cluster
   • DB engine version: Target major version to upgrade to
   • Data storage type: Data storage type
3. Click [Next].

Step 2. Review precautions and start migration

1. Review the precautions and select the checkbox for each item.
2. Click [Start migration].

Step 3. Check migration progress

You can check the following statuses in the DB Server list:

Step 4. Perform the Major Version Upgrade

1. Select the new cluster in the Waiting for upgrade state.
2. On the details page, click [Major Version Upgrade].
3. Review the precautions and select the checkbox.
4. Click [Start upgrade].

Step 5. Complete the upgrade

1. When pg_upgrade is completed, the status of the new cluster changes to Running.
2. Verify that you can connect to the new cluster successfully.
3. You can return or retain the existing cluster as needed.

Manage schema

PostgreSQL provides Default Schema named Public when creating a Database and gives access to all users (PUBLIC).
However, it is recommended to create a separate Schema that serves a particular purpose because using a Public Schema can be a security vulnerability.
In addition, the following access permissions have been removed from the newly created Database at the request of many customers and certification evaluation authorities:

revoke all on schema public from public;

Therefore, we recommend that you access the owner account of Database and create a separate schema as follows:

create schema [schema name];

How to access DB Server.

How to use Private Domain.

Cloud DB for PostgreSQL provides Private Domain and the Private Domain name is connected to the IP of the DB Server.
With Standalone configuration, it connects to the IP of one DB Server.
With HA configuration, the Primary DB Server and the Secondary DB Server each have a different Private Domain, but both are connected to the IP of the Primary DB Server. Any Private Domain used will connect to the Primary DB Server. When a Failover occurs, the connection information is automatically changed to the newly promoted Primary DB Server, making it easy to manage access information.

Examples of access information include: (If using JDBC)

jdbc:postgresql://<Private Domain name>:<port>/<DB name>

How to use a private IP

Cloud DB for PostgreSQL supports DB Server connection via a private IP. The private IP is the DB Server IP that does not change even if a Failover occurs. It is useful when you use access information while being familiar with the concept of private IP, and use Read Only DB while connecting Secondary DB Server.
However, if Secondary DB Server suffers a heavy load, the HA configuration may be affected and failed to Failover. In this case, add Read Replica DB instead of using a Secondary DB, and distribute the read load using Load Balancer.

Examples of access information include: (If using JDBC)

- When accessing Primary DB Server
jdbc:postgresql://<Primary private IP>:<port>,<Secondary private IP>:<port>/<DB name>?targetServerType=primary

- When accessing Secondary DB Server
jdbc:postgresql://<Primary private IP>:<port>,<Secondary private IP>:<port>/<DB name>?targetServerType=secondary

Manage operation system

Update the operating system of the DB Server to the latest version provided by NAVER Cloud Platform.
The operating system update is applied to the entire DB Service and proceeds one server at a time in the following order: Secondary → Read Replica → Primary. During the update process, server access is not available. To update the Primary DB Server, click the Failover and OS Version Upgrade button.

Updating the operating system of Secondary and Read Replica Servers

The update is performed one server at a time in the order of Secondary, then Read Replica. During the update, access to the server being updated is restricted.

1. To update the server's operating system version, click OS Management, review the popup window, and then click [Next].
   • Operating System Update
     
   • Kernel Update
     
   Caution

   • If the subnet that includes the DB service does not have enough available IPs, the OS update cannot be performed.
   • Make sure that the Subnet includes enough available IPs for all DB Servers in the DB Service that require the OS update before proceeding.
2. After reviewing the precautions for the operating system update, click the checkbox.
3. Once you’ve confirmed all items, click [Upgrade].
   • Operating System Update
     
   • Kernel Update
     
4. After reviewing the precautions for updating, click [Yes].
   
5. You can monitor the update progress through the DB Server status.
   

Updating the operating system of the Primary Server

After performing Failover, update the OS of the Secondary (Prior Primary) Server.

1. To update the operating system version of the Primary Server, select the server and click [Failover and OS Version Upgrade].
   

2. After reviewing the precautions for updating the Primary Server’s OS, click [Upgrade].

   

3. You can monitor the update progress through the DB Server status.
   

Change return protection settings

You can change the return protection settings for the selected server. Return protection applies only to Primary DB servers and Stand Alone DB servers. When return protection is enabled, the corresponding DB Server cannot be deleted. During the change of return protection settings, no server downtime occurs, and the DB Server remains accessible.
To change:

• For DB Servers with return protection disabled, the Configure return protection popup window appears. Confirm the DB Service name and click [Yes].
  

• For DB Servers with return protection enabled, the Disable return protection popup window appears. Confirm the DB Service name and click [Yes].
  

For servers configured with high availability, return protection can be set only on the Primary Server. However, even if return protection is enabled on the Primary Server, the server can be returned in the following case:

• When high availability is disabled, the Secondary Server is automatically returned.

With return protection enabled, creating a new service transfers return protection settings. Return protection settings are delegated in the following cases:

• Create a new service based on a backup file.