hx-postgresql-advisor

Guides PostgreSQL planning, installation, and validation on HX-9 within HX architecture authority.

Updated Sep 9, 2026
One-click install
npx skills add https://github.com/HX-Infratstructure/HX-Eco-System --skill hx-postgresql-advisor-hx-infratstructure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hx-postgresql-advisor
Source: https://github.com/HX-Infratstructure/HX-Eco-System/tree/main/skills/postgresql/hx-postgresql-advisor
Command: npx skills add https://github.com/HX-Infratstructure/HX-Eco-System --skill hx-postgresql-advisor-hx-infratstructure

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? PostgreSQL work inside the HX Eco-System risks being derailed by generic tutorials, managed-service assumptions, or third-party advice that conflicts with HX's native-Linux, systemd-based architecture and strict validation gates. This Skill reconciles current PostgreSQL Global Development Group documentation and reviewed external expertise against HX authority so recommendations never override server placement, deployment standards, or smoke-test criteria. ## Core Features & Use Cases - Authority reconciliation: Classifies every material recommendation as ACCEPT, ADAPT, REJECT_FOR_HX, or OWNER_DECISION_REQUIRED against a defined precedence chain from owner decisions down to general model knowledge. - HX-9 deployment discipline: Enforces native systemd deployment, shared-host boundaries with Redis, version/package-source pinning, and network/authentication rules before any configuration change. - Governed validation: Anchors acceptance to the exact PostgreSQL smoke-test contract (TEMP table known-answer proof, MCP companion gate, reboot persistence) rather than vendor quickstarts. - Use Case: When planning the HX-9 PostgreSQL build, use this Skill to verify the current supported PostgreSQL major against PGDG guidance, flag unpinned decisions like package source or listener configuration as OWNER_DECISION_REQUIRED, and reject container-based deployment suggestions. ## Quick Start Ask the agent to plan the HX-9 PostgreSQL installation using the HX PostgreSQL Advisor and identify which decisions require owner approval before execution.

Frequently Asked Questions about hx-postgresql-advisor

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

FAQPage Schema
How do I plan a PostgreSQL installation on HX-9?▼

Establish the HX-9 host context, build state, and shared-host boundary with Redis first, then verify the current PostgreSQL major against PGDG versioning policy. Unpinned choices like package source, data directory, or listener configuration must be returned as OWNER_DECISION_REQUIRED rather than defaulted.

What PostgreSQL version should I deploy on Ubuntu?▼

The Skill does not choose the HX major version; that is an owner decision pinned in the HX-9 runbook. It verifies current PGDG support policy, recommends the current minor within an accepted supported major, and rejects beta releases like PostgreSQL 19 as normal BASE.

Can I use Docker or managed PostgreSQL instead of native installation?▼

No, containers and managed services like Neon Cloud are classified REJECT_FOR_HX unless the owner explicitly changes the architecture. HX mandates native Ubuntu Linux with systemd for PostgreSQL on HX-9.

How is PostgreSQL acceptance validated in the HX Eco-System?▼

Acceptance follows smoke-tests/postgresql-smoke-test.md: a remote runner from HX-5 connects to the HX-9 listener, creates a TEMP table, inserts and reads a known token, proves the table is absent in a new session, then passes the MCP companion gate and reboot persistence check.

When should PostgreSQL tuning or connection pooling be applied?▼

Tuning memory, WAL, checkpoints, or autovacuum requires captured hardware, workload, and measurement evidence first, never formula alone. PgBouncer, HA, replication, and backup topology are all OWNER_DECISION_REQUIRED and are not BASE assumptions.