postgresql-best-practices/SOURCE.md

Independent packaging and use boundaries

Pinned source: https://github.com/microsoft/postgres-skills/tree/9ba96abc800a574a0872f3d6b912ea8be1a6735e/plugin/skills/postgresql-best-practices Publisher: Microsoft. License: MIT; keep the complete notice in LICENSE.upstream.txt. All 24 original skill/reference files are preserved byte for byte with their relative layout. Five source-context/license files are also preserved. The MCP and plugin configuration copies are renamed and stored as reference material; this instruction package does not install or launch an MCP server. BB Skills assembled this download independently; it is not an official Microsoft plugin release or a certification.

Read SOURCE.md before choosing an execution path. The source describes both generic PostgreSQL and Azure-specific workflows. For live database work, its router expects a separately installed postgres-mcp server and a user-selected connection. Node.js/npx, an AI client and the database role are external prerequisites. Azure control-plane operations additionally need the user's authenticated Azure CLI and correct service flavor. Downloading this ZIP creates no connection, approval, extension, service or model account.

Use a dedicated least-privilege database role and an explicitly read-only profile for exploration. The effective database privileges matter; a client label or an instruction is not an access-control boundary. Any data or query result passed to a client becomes part of that client interaction. Upstream telemetry settings do not determine the AI provider's data policy. Keep credentials out of prompts and command arguments.

Review each proposed operation for the actual database version, workload and service. Plain EXPLAIN describes a plan; EXPLAIN ANALYZE executes the statement and can have effects. A SELECT can call functions with side effects, and a rollback is not a general way to undo external effects. Use a bounded non-production fixture for experiments.

CONCURRENTLY is not available for every index operation or table type and cannot be used for CREATE INDEX inside a transaction block. Do not apply the source's broad production-indexing rule without checking the exact operation and PostgreSQL documentation. RLS behavior depends on the effective role and policy: superusers and BYPASSRLS roles bypass policies; a SECURITY DEFINER function's effect depends on its owner's privileges and configuration. The preserved source's short checklist is context, not a complete authorization design.

The BB Skills local scenario checks selected plan, index and role behavior on synthetic data in PostgreSQL 17. It does not run this skill through an AI client or postgres-mcp, validate every recommendation, test RLS, extensions, replication, vector search, Azure or model services, or certify a production database. All original references, including untested Azure guidance, are included so the package is not a broken router.

The instruction files are free under MIT. An AI/model plan, Azure resources, hosting or other services can have separate charges. Our recorded fixture starts no cloud resources and makes no paid model call. Do not interpret this free catalog download as approval to incur those costs.

The upstream README and setup copies retain their original relative links as source context; follow the pinned repository for those installation links. The actual SKILL.md reference links resolve inside this package.