postgresql-best-practices

name	postgresql-best-practices
description	Expert PostgreSQL skills with intelligent routing. Covers both generic PostgreSQL and Azure Database for PostgreSQL.
tags	["postgresql","azure","database","skills","routing"]
activation	{"user_intent":["work with PostgreSQL","database query","connect to postgres","Azure PostgreSQL","show tables","list tables","describe schema","database schema","what tables exist"],"technical_keywords":["postgresql","postgres","psql","pg_","azure database for postgresql","flexible server","pgvector","diskann","pgsql_","postgres-mcp"]}

PostgreSQL Agent Skills — Routing Table

Use references as supplemental context — combine them with your PostgreSQL knowledge. If reference guidance is incomplete, answer with appropriate caveats rather than inventing details.

Key Constraints

• Never use ALTER SYSTEM on managed services — use portal/CLI/ARM instead
• Never assume SUPERUSER — use azure_pg_admin (Azure) or equivalent managed role
• Use CONCURRENTLY for CREATE INDEX / REINDEX / DETACH PARTITION in production
• pgsql_modify does NOT return row data (no RETURNING support)
• Destructive DDL confirmation: Before executing pgsql_modify with DROP, TRUNCATE, (without WHERE), or , always ask the user for explicit confirmation. List the affected objects and warn about data loss before proceeding.