Postgres

Click Deploy on the Postgres card. CloudHike.dev creates a database named app and a non-superuser role that owns it, then shows the connection string with Reveal, Copy, Reset password and Delete.

After upgrading, a Pro user can move a shared database to its own container from the Postgres card. Writes pause while it is copied, every table's row count is checked against the original, and the old copy is kept closed for 7 days before it is dropped.

The connection string is in DATABASE_URL. When TLS is on, it ends in ?sslmode=require and the public port accepts only encrypted connections.

The pooler lends a real connection for one transaction at a time. Prepared statements work. Anything that has to last longer than a transaction on one connection needs DIRECT_URL.

psql "$DATABASE_URL"

import { Pool } from "pg";

const pool = new Pool({ connectionString: process.env.DATABASE_URL });
const { rows } = await pool.query("select * from todos where done = $1", [false]);

import { drizzle } from "drizzle-orm/node-postgres";
import { Pool } from "pg";

// One pool per process, kept across dev hot reloads.
const globalForDb = globalThis as unknown as { pool?: Pool };
const pool = globalForDb.pool ?? new Pool({ connectionString: process.env.DATABASE_URL, max: 5 });
if (process.env.NODE_ENV !== "production") globalForDb.pool = pool;

export const db = drizzle(pool);

import os, psycopg

with psycopg.connect(os.environ["DATABASE_URL"]) as conn:
    print(conn.execute("select version()").fetchone())

• Connections idle for 5 minutes are closed by the server. Pools open a new one on their next query.
• Once a database uses half its connection limit, the usage check (every 5 minutes) closes connections that have been idle for over a minute, such as those a dev server leaves behind on hot reload. Running queries are never touched.
• If you see too many connections for role, click Close idle connections on any tab of Open database to free the limit right away.
• The Usage page shows each database's connections and marks one Maxed out for a day after it hit its limit.

Click Open database on a ready Postgres card to browse and query without installing anything.

Everything is read-only until you switch off Read-only in the SQL editor. Each query has a 10 second statement timeout and a 3 second lock timeout. With writes allowed, a script runs in one transaction that commits only if every statement succeeds, and statements like DROP, DELETE and UPDATE ask for confirmation.

A nightly job at 02:00 runs pg_dump for every running database and stores the dump in the project's storage bucket under _backups/postgres/. Without a Storage service, it uses the platform's backup bucket instead.

• Retention is set on the Backups tab: up to 7 days on Free and 30 on Pro. The newest backup is always kept.
• Take a backup at any time with the Backup now button.
• Download a backup through a short-lived signed link.
• Restore first takes a safety backup, loads the dump into a new database next to the live one, and swaps them only after it fully loads. A failed restore leaves your database untouched.
• Backups stop when storage would pass 98% of the plan limit.

• A database over its size limit gets a warning from the usage check. After 3 days over, it becomes read-only until you free space or upgrade.
• Free databases with no connections for 6 hours are stopped. Click Wake on the card to start one again.
• Click Pause on the card to stop a database yourself. Your data is kept, and compute is not charged while it is paused. Click Resume to start it again.
• Reset password creates a new password and updates DATABASE_URL. Apps still using the old password are disconnected until you update them.