pg.ddx.io: the PostgreSQL community's memory MCP Resources
pg.ddx.io: the PostgreSQL community's memory offers 113 resources. A resource is data the server exposes for a client to attach as context — a file, a page, an API response — rather than an action. Each has its own page, per client.
-
community/coding-conventions.md -
community/common-pitfalls.md -
community/communication-norms.md -
community/conventions/code-comments.md -
community/conventions/commit-message-format.md -
community/conventions/committing-checklist.md -
community/conventions/creating-clean-patches.md -
community/conventions/extension-conventions.md -
community/conventions/git-workflow.md -
community/conventions/pgindent.md -
community/conventions/sql-style.md -
community/conventions/whitespace-and-encoding.md -
community/decision-making.md -
community/methodology.md -
community/patch-submission.md -
community/ready-for-committer-to-committed.md -
community/review-standards.md -
community/voices/andres-freund.md -
community/voices/index.md -
community/voices/michael-paquier.md -
community/voices/robert-haas.md -
community/voices/tom-lane.md -
community/voices/tomas-vondra.md -
examples/find-all-vacuum-discussions.md -
examples/how-was-wal-implemented.md -
examples/review-a-patch-series.md -
examples/trace-index-am-evolution.md -
generic/mcp-servers.json -
generic/workflows/bug-investigation.md -
generic/workflows/build-and-test.md -
generic/workflows/buildfarm-blame.md -
generic/workflows/commitfest-health-watch.md -
generic/workflows/debug-backend.md -
generic/workflows/debug-initdb.md -
generic/workflows/deep-git-blame.md -
generic/workflows/fetch-patch-test.md -
generic/workflows/find-related-patches.md -
generic/workflows/forward-port-cold-branch.md -
generic/workflows/gain-perspective.md -
generic/workflows/package-an-extension.md -
generic/workflows/perf-testing.md -
generic/workflows/pre-review-by-committers.md -
generic/workflows/rebase-feature-branch.md -
generic/workflows/research-and-connect-dots.md -
generic/workflows/review-thread-context.md -
generic/workflows/semantic-code-search.md -
generic/workflows/submit-patch.md -
generic/workflows/trace-feature-history.md -
generic/workflows/use-psql-effectively.md -
generic/workflows/write-an-extension.md -
generic/workflows/write-plpgsql.md -
postgres-best-practices -
postgres/best-practices/references/_sections.md -
postgres/best-practices/references/_template.md -
postgres/best-practices/references/advanced-full-text-search.md -
postgres/best-practices/references/advanced-jsonb-indexing.md -
postgres/best-practices/references/conn-idle-timeout.md -
postgres/best-practices/references/conn-limits.md -
postgres/best-practices/references/conn-pool-modes.md -
postgres/best-practices/references/conn-pooling.md -
postgres/best-practices/references/conn-prepared-statements.md -
postgres/best-practices/references/data-batch-inserts.md -
postgres/best-practices/references/data-n-plus-one.md -
postgres/best-practices/references/data-pagination.md -
postgres/best-practices/references/data-upsert.md -
postgres/best-practices/references/lock-advisory.md -
postgres/best-practices/references/lock-deadlock-prevention.md -
postgres/best-practices/references/lock-short-transactions.md -
postgres/best-practices/references/lock-skip-locked.md -
postgres/best-practices/references/monitor-bloat.md -
postgres/best-practices/references/monitor-explain-analyze.md -
postgres/best-practices/references/monitor-locks.md -
postgres/best-practices/references/monitor-pg-stat-statements.md -
postgres/best-practices/references/ops-autovacuum.md -
postgres/best-practices/references/ops-extension-upgrades.md -
postgres/best-practices/references/ops-logical-replication.md -
postgres/best-practices/references/ops-migration-safety.md -
postgres/best-practices/references/ops-timeout-hygiene.md -
postgres/best-practices/references/query-composite-indexes.md -
postgres/best-practices/references/query-covering-indexes.md -
postgres/best-practices/references/query-index-types.md -
postgres/best-practices/references/query-missing-indexes.md -
postgres/best-practices/references/query-not-in-null.md -
postgres/best-practices/references/query-partial-indexes.md -
postgres/best-practices/references/schema-constraints.md -
postgres/best-practices/references/schema-data-types.md -
postgres/best-practices/references/schema-enum-vs-lookup.md -
postgres/best-practices/references/schema-foreign-key-indexes.md -
postgres/best-practices/references/schema-lowercase-identifiers.md -
postgres/best-practices/references/schema-partitioning.md -
postgres/best-practices/references/schema-primary-keys.md -
postgres/best-practices/references/schema-timestamptz.md -
postgres/best-practices/references/security-privileges.md -
postgres/best-practices/references/security-rls-basics.md -
postgres/best-practices/references/security-rls-performance.md -
postgres-dba -
postgres-developer -
postgres-overseer -
postgres-replication -
postgres-triage -
postgres-user -
steering/postgresql.md -
benchmark -
choose-instance -
flex-bison-to-lime -
pg-benchmark-rigor -
tooling/pg-benchmark-rigor/references/sources.md -
pg-ddx-research -
pg-numa-benchmark -
pg-patch-upkeep -
tooling/review-as-author/LICENSE -
review-as-author -
tune-os-for-benchmark
pg.ddx.io: the PostgreSQL community's memory also offers 10 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 5 November 2026.
A listing does not declare its resources, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each resource's type and contents.