> For the complete documentation index, see [llms.txt](https://docs.vngcloud.vn/vng-cloud-document/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vngcloud.vn/vng-cloud-document/vdb/relational-database-service-rds/postgresql-standalone.md).

# PostgreSQL Standalone

## Overview

**PostgreSQL Standalone** (Single Node) is a PostgreSQL deployment model on vDB with a **single node**, suitable for development, testing environments, or small applications that do not require High Availability.

### What is PostgreSQL Standalone?

In the Standalone model, all database operations — including reads and writes — are handled by a **single node**:

* **Single Node**: Handles all read and write operations (SELECT, INSERT, UPDATE, DELETE) on the same instance.
* **Simple deployment**: No replication or failover configuration required.
* **Lower cost**: Suitable for workloads that do not require high availability.

### Single Node vs. Cluster Comparison

| Feature               | Single Node                              | Cluster                                                          |
| --------------------- | ---------------------------------------- | ---------------------------------------------------------------- |
| **Architecture**      | 1 single node                            | 1 Writer + N Readers                                             |
| **High Availability** | No                                       | Yes (Automatic Failover)                                         |
| **Scale Read**        | No                                       | Yes (Read traffic distributed to Readers)                        |
| **Backup**            | Automatic daily backup (legacy)          | Integrated with Backup Center (Auto Backup + Manual Backup)      |
| **Number of nodes**   | 1                                        | 2 - 10                                                           |
| **Use Case**          | Development, Testing, small applications | Production, Mission-critical, applications requiring high uptime |

### When should you use PostgreSQL Standalone?

* **Development & Testing**: Environments that do not require high uptime.
* **Small applications**: Applications with low traffic that do not need read scaling.
* **Cost optimization**: When High Availability is not a top priority.

{% hint style="info" %}
**Note:**

* **Single Node** is suitable for **development** and **testing** environments due to simpler configuration and lower cost.
* **Cluster** is recommended for **production** environments when High Availability and fault tolerance are required.
  {% endhint %}

***

## Limitations and Notes

{% hint style="info" %}
**About Reserved Usernames:**

When creating an instance, you **must not** use the following usernames as the Master Username as they are reserved by the system: `postgres`, `admin`, `cron_admin`, `robot_zmon`, `vngpooler`, `vngpam`, `vngrep`, `vngsuperrole`.
{% endhint %}

{% hint style="info" %}
**About Deployment Type:**

PostgreSQL Standalone uses the **Single Node** deployment type. If you need High Availability and read scaling, consider using [PostgreSQL Cluster](/vng-cloud-document/vdb/relational-database-service-rds/postgresql-cluster.md).
{% endhint %}

{% hint style="warning" %}
**Deployment Type conversion is not supported:**

vDB currently does not support converting from Standalone to Cluster after an instance has been created. To migrate, you need to create a new PostgreSQL Cluster and [migrate the data](/vng-cloud-document/vdb/relational-database-service-rds/postgresql-cluster/migrate-from-postgresql-single-to-cluster.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vngcloud.vn/vng-cloud-document/vdb/relational-database-service-rds/postgresql-standalone.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.