PostgreSQL

Advanced open-source relational database. Recognized for its robustness, compliance with SQL standards, and native support for complex data types such as JSON, arrays, and geospatial data.

Version:

17.8

back to Marketplace

VM Requisites

Resource Minimun
CPU 2 vCPU
RAM 4 GB
Disk 40 GB
Operating System Ubuntu 22.04 / 24.04

Access Port

Port Protocol Usage
30432 TCP PostgreSQL protocol

How To Access

With psql

# Connect as application user
psql -h <VM_IP> -p 30432 -U <USERNAME> -d <DATABASE>

# Connect as postgres (superuser)
psql -h <VM_IP> -p 30432 -U postgres

Connection string for applications

postgresql://<USERNAME>:<PASSWORD>@<VM_IP>:30432/<DATABASE>

Examples by language

# Python (psycopg2)
import psycopg2
conn = psycopg2.connect( 
host="<VM_IP>", port=30432, 
user="<USER>", password="<PASSWORD>", dbname="<DATABASE>"
)
// Node.js (pg)
const client = new Client({ 
host: "<VM_IP>", port: 30432, 
user: "<USER>", password: "<PASSWORD>", database: "<DATABASE>"
});
#Python (SQLAlchemy)
engine = create_engine("postgresql://<USER>:<PASSWORD>@<VM_IP>:30432/<DATABASE>")

Verify that PostgreSQL is active

# View the PostgreSQL pod
`kubectl get pods -A | grep postgresql`

# View the installation log
`tail -f /var/log/cuemby/bootstrap.log`

# Verify that the port is listening
`ss -tlnp | grep 30432`

Expected output

NAME                          READY   STATUS    RESTARTS
postgresql-xxxxxxxxx-xxxxx    1/1     Running   0        ← Running ✓

Configuration Parameters

Credentials and database

Parameter Default Description
POSTGRES_PASSWORD ⚠️ auto-generated Application user password. If left blank, Cuemby generates a random one.
POSTGRES_USER cuemby Application username.
POSTGRES_DB app Name of the database automatically created upon deployment.
POSTGRESQL_DATA_SIZE 20Gi Persistent volume size for databases.

Performance tuning

Parameter Default Description
POSTGRESQL_MAX_CONNECTIONS 100 Maximum number of simultaneous connections. Increase with caution: each connection consumes memory.
POSTGRESQL_SHARED_BUFFERS 128MB Memory reserved for data cache. Recommended: 25% of total RAM.
POSTGRESQL_WORK_MEM 4MB Memory usage per sorting or hashing operation. Multiply by MAX_CONNECTIONS to estimate total usage.

💡 For a VM with 4 GB of RAM, a balanced configuration would be: SHARED_BUFFERS=1GB, WORK_MEM=16MB, MAX_CONNECTIONS=100.

First Steps (quick start)

-- List databases
\l

-- Connect to the application database
\c app

-- Create a table
CREATE TABLE users (
id SERIAL PRIMARY KEY,
name VARCHAR(100) NOT NULL,
email VARCHAR(150) UNIQUE NOT NULL,
created_in TIMESTAMPTZ DEFAULT NOW()
);

-- Insert a record
INSERT INTO users (name, email) VALUES ('Martin', 'martin@cuemby.com');

-- Query
SELECT * FROM users;

-- View existing tables
\dt

Quick Troubleshooting

Problem Probable cause Solution
password authentication failed Incorrect password Review the deployment outputs in the Cuemby portal.
could not connect to server PostgreSQL still getting started Wait ~2–3 min and check tail -f /var/log/cuemby/bootstrap.log.
too many connections MAX_CONNECTIONS reached Use a connection pooler like PgBouncer or increase POSTGRESQL_MAX_CONNECTIONS.
out of shared memory SHARED_BUFFERS very high Reduce SHARED_BUFFERS to no more than 25% of available RAM.
Pod in CrashLoopBackOff Insufficient disk space or RAM Check with kubectl describe pod -n .

Cuemby Cloud

IaaS

About Cuemby Cloud

Cuemby Cloud is enterprise-grade cloud infrastructure managed from a single console, built for stronger security, predictable operations, and easy scaling across regions.

Datacenters regions available in Colombia, Ecuador, and Chile

Backed by Tier III / Tier IV data center locations

Zero Network Ingress and Egress Fees

24/7 local expert support

Ready to Modernize Your Enterprise?

Future challenges demand future-ready solutions.
Let’s get started!

© Copyright | Cuemby® 2025