postgres

Installs and manages a local PostgreSQL 18 database on a private box.

2|Updated Jun 26, 2026
One-click install
npx skills add https://github.com/otenycom/talents --skill postgres-otenycom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: postgres
Source: https://github.com/otenycom/talents/tree/main/skills/postgres
Command: npx skills add https://github.com/otenycom/talents --skill postgres-otenycom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Setting up PostgreSQL normally requires root access, apt packages, and manual configuration. This Skill installs PostgreSQL 18 entirely in user space under ~/postgres, with no apt and no extra server, giving the owner a private local database on demand. ## Core Features & Use Cases - User-space installation: Downloads a pinned, checksum-verified PostgreSQL 18 binary tarball and installs it under ~/postgres without system package managers. - Idempotent service management: Starts the cluster via ensure_postgres.sh, handles stale postmaster.pid files, adopts legacy clusters, and registers the database as a managed service on 127.0.0.1:5432. - Use Case: An owner types "I need a local database" in chat; the Skill confirms intent, installs PostgreSQL 18, starts it on loopback only, and registers it so it restarts automatically later. ## Quick Start Ask the assistant to install a local PostgreSQL database and confirm when it asks whether to proceed.

Frequently Asked Questions about postgres

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install PostgreSQL without apt or root access?▼

Run the install_postgres.sh script, which downloads a pinned PostgreSQL 18 binary tarball, verifies its SHA-256 checksum, and extracts it under ~/postgres. It then runs initdb and configures the cluster to listen on 127.0.0.1 only.

How to start a local PostgreSQL database on port 5432?▼

Run ensure_postgres.sh, which starts the cluster with pg_ctl on 127.0.0.1:5432 and waits until the port accepts connections. It is idempotent, so running it when PostgreSQL is already up simply prints POSTGRES_UP.

Does this PostgreSQL setup listen on the public internet?▼

No. The cluster is configured with listen_addresses set to 127.0.0.1, so it only accepts connections from the same box. Nothing is opened to the internet and no public website is published.

What happens if a legacy PostgreSQL cluster already exists?▼

If ~/odoo-site/pgdata exists and ~/postgres/data does not, the installer adopts the existing cluster instead of running initdb again. It never creates a second cluster and never runs pg_upgrade.

Why does PostgreSQL fail to start after moving to a new container?▼

A carried cluster may pin lc_* locale settings like en_US.UTF-8 that the new container image lacks. The normalize_pg_locales.py script rewrites unavailable locales to C.UTF-8 in postgresql.conf before startup.

What are the limitations of this PostgreSQL installer?▼

It supports only x86_64 Linux and pins PostgreSQL 18.6.0. It maintains exactly one cluster, does not publish any public endpoint, and never installs via apt or starts the database without an explicit owner request.