pg.ddx.io: the PostgreSQL community's memory

io.ddx.pg/archiveVersion 2026.10.22

Every PostgreSQL mailing list since 1991, linked to the commits, code, commitfest and docs.

Status

Responds266 msNov 14, 2026, 14:34 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 14:34 UTC
Latency: 266 ms
Remotes responding: 1 of 2
Sign-in: No sign-in, Sign-in unknown
Hosting: Hosted outside the EU (detected)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://pg.ddx.io/mcpResponds266 msNov 14, 2026, 14:34 UTC

No sign-in

Claude Code

claude mcp add --transport http archive https://pg.ddx.io/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: archive
Remote MCP server URL: https://pg.ddx.io/mcp

Cursor

{
  "mcpServers": {
    "archive": {
      "url": "https://pg.ddx.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"archive","type":"http","url":"https://pg.ddx.io/mcp"}'

SSE

https://pg.ddx.io/mcp/sseNot checkedUses SSE

Uses SSE (legacy), not checked

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

126 tools

Tools of pg.ddx.io: the PostgreSQL community's memory
	Description		Read-only	Idempotent	Open world
`animal_history`Run timeline for one animal. Filterable by branch and start cutoff; ordered newest first.	Run timeline for one animal. Filterable by branch and start cutoff; ordered newest first.	No	Yes	No	Yes
`animal_owner_contributions`Animals run by one owner: list, branches each tracks, last status, first_seen_at and elapsed days since first observation.	Animals run by one owner: list, branches each tracks, last status, first_seen_at and elapsed days since first observation.	No	Yes	No	Yes
`blame`Per-line blame of a postgres file at any commit (code-history index): the commit that wrote each line, as `git blame` with git's default diff. ignore_revs (default true) passes through the pgindent/reformat commits of .git-blame-ignore-revs when they replaced lines one-for-one; reverse adds the commit that removed each line later on the version's branch. At most 2000 lines per call; commits lists author, date and subject per short sha. proposals=true adds, per line, the earliest posted patch (Message-ID, date) on its commit's threads that added it; proposals_complete=false when the window spans more than 10 commits (those with the most lines are read). Lines under 4 characters or without a letter or digit get none. Not the same as git_blame, which returns a file's commit history.	Per-line blame of a postgres file at any commit (code-history index): the commit that wrote each line, as `git blame` with git's default diff. ignore_revs (default true) passes through the pgindent/reformat commits of .git-blame-ignore-revs when they replaced lines one-for-one; reverse adds the commit that removed each line later on the version's branch. At most 2000 lines per call; commits lists author, date and subject per short sha. proposals=true adds, per line, the earliest posted patch (Message-ID, date) on its commit's threads that added it; proposals_complete=false when the window spans more than 10 commits (those with the most lines are read). Lines under 4 characters or without a letter or digit get none. Not the same as git_blame, which returns a file's commit history.	No	Yes	Yes	No
`blame_symbol`Show the commit history that modified a symbol's file, filtered to the symbol's line range.	Show the commit history that modified a symbol's file, filtered to the symbol's line range.	No	Yes	No	Yes
`browse_by_date`Browse threads within a specific date range. Useful for exploring what was discussed during a particular time period.	Browse threads within a specific date range. Useful for exploring what was discussed during a particular time period.	No	Yes	No	Yes
`build_status_freshness`Most recent :entry/last-build-at observation across all entries. Use to detect a stalled cfbot scraper.	Most recent :entry/last-build-at observation across all entries. Use to detect a stalled cfbot scraper.	No	Yes	No	Yes
`buildfarm_overview`High-level buildfarm health: animal count, recent run counts, currently-failing animals, top owners, OS / branch breakdown, and freshness.	High-level buildfarm health: animal count, recent run counts, currently-failing animals, top owners, OS / branch breakdown, and freshness.	No	Yes	No	Yes
`calendar_feeds`List every pg.ddx.io calendar feed (iCalendar URLs) with event counts: all events, regions, countries, conference series, the PostgreSQL release cycle, teams and organisations.	List every pg.ddx.io calendar feed (iCalendar URLs) with event counts: all events, regions, countries, conference series, the PostgreSQL release cycle, teams and organisations.	No	Yes	Yes	No
`check_upstream_status`Check whether a pull request has been merged upstream. Returns the latest patch series head commit and any merge information.	Check whether a pull request has been merged upstream. Returns the latest patch series head commit and any merge information.	No	Yes	No	Yes
`code_index_status`Get code indexing statistics: files indexed, symbol counts by kind and language, edge count, community count.	Get code indexing statistics: files indexed, symbol counts by kind and language, edge count, community count.	No	Yes	No	Yes
`code_search`Search the postgres source at any commit, branch, tag or date (or across history), from the code-history index: every line of every commit, byte-exact. A literal by default; match=regex for a PostgreSQL regex (^ and $ are per line; \b \< \> as in grep), match=identifier for any of snake_case/CamelCase/UPPER spellings. File sets agree with `git grep -l` at the same commit. Results name the resolved sha and ref. complete=false means the totals are lower bounds (cut says why). With history (all \| <rev> \| A..B) it returns every matching line any commit in the range had, with the commit that added it and the one that removed it.	Search the postgres source at any commit, branch, tag or date (or across history), from the code-history index: every line of every commit, byte-exact. A literal by default; match=regex for a PostgreSQL regex (^ and $ are per line; \b \< \> as in grep), match=identifier for any of snake_case/CamelCase/UPPER spellings. File sets agree with `git grep -l` at the same commit. Results name the resolved sha and ref. complete=false means the totals are lower bounds (cut says why). With history (all \| <rev> \| A..B) it returns every matching line any commit in the range had, with the commit that added it and the one that removed it.	No	Yes	Yes	No
`codebase_map`Get a directory-level overview of the codebase showing file counts and symbol counts per directory.	Get a directory-level overview of the codebase showing file counts and symbol counts per directory.	No	Yes	No	Yes
`combine_calendars`Combine several pg.ddx.io calendar feeds into ONE subscription. Give feed paths or URLs as listed by calendar_feeds (e.g. events/region/europe, series/pgconf-eu, teams/committers, people/<8hex>, https://pg.ddx.io/cal/orgs/edb.ics; 1-200). Returns the combined feed's hash, canonical feed list, https url and webcal url. The same selection always yields the same URL.	Combine several pg.ddx.io calendar feeds into ONE subscription. Give feed paths or URLs as listed by calendar_feeds (e.g. events/region/europe, series/pgconf-eu, teams/committers, people/<8hex>, https://pg.ddx.io/cal/orgs/edb.ics; 1-200). Returns the combined feed's hash, canonical feed list, https url and webcal url. The same selection always yields the same URL.	No	No	Yes	No
`commit_buildfarm_status`Buildfarm results for one PostgreSQL commit: every animal that built it, with branch, status (passed/failed/flapping), the failing stage and the log url, plus a {passed, failed, flapping, unknown} rollup. commit_sha is a SHA (>= 7 hex) or a branch, tag or major version (17, 9.6) for the commit it points at. Cite the commit SHA and the log urls.	Buildfarm results for one PostgreSQL commit: every animal that built it, with branch, status (passed/failed/flapping), the failing stage and the log url, plus a {passed, failed, flapping, unknown} rollup. commit_sha is a SHA (>= 7 hex) or a branch, tag or major version (17, 9.6) for the commit it points at. Cite the commit SHA and the log urls.	No	Yes	No	Yes
`commit_history`Everything linked to one commit: subject, author and date with its sha, the mail thread its Discussion: link names (participants resolved to people and organizations), the commitfest entry if tracked, and Discord mentions. For postgres also first_releases (per branch the change landed on: branch, sha, release e.g. 14.23 or null when unreleased, first_version incl. betas, shipped=false when it was reverted before that release), reverted_by (the commits that revert it, each with its own reverted_by) and reverts, read from git tags and commit messages, never guessed. commit_id takes a SHA (>= 7 hex), branch, tag, major version (17, 9.6), <ref>~N or a commit_id from another tool; repository defaults to postgres. The diff itself is not included (git_diff, or git_show_file for one file). Cite the sha and the thread's https://postgr.es/m/<message_id>.	Everything linked to one commit: subject, author and date with its sha, the mail thread its Discussion: link names (participants resolved to people and organizations), the commitfest entry if tracked, and Discord mentions. For postgres also first_releases (per branch the change landed on: branch, sha, release e.g. 14.23 or null when unreleased, first_version incl. betas, shipped=false when it was reverted before that release), reverted_by (the commits that revert it, each with its own reverted_by) and reverts, read from git tags and commit messages, never guessed. commit_id takes a SHA (>= 7 hex), branch, tag, major version (17, 9.6), <ref>~N or a commit_id from another tool; repository defaults to postgres. The diff itself is not included (git_diff, or git_show_file for one file). Cite the sha and the thread's https://postgr.es/m/<message_id>.	No	Yes	No	Yes
`commitfest_stats`Overview of all indexed commitfests: count by status, top contributors (entries authored), distinct people / commitfests / entries totals.	Overview of all indexed commitfests: count by status, top contributors (entries authored), distinct people / commitfests / entries totals.	No	Yes	No	Yes
`contribution_summary`Summary of contribution counts per release: unique people, distinct commits, role breakdown (count(DISTINCT commit_sha) per role, canonical authoritative repos only), and revert-commit count. Powers the /community hero strip.	Summary of contribution counts per release: unique people, distinct commits, role breakdown (count(DISTINCT commit_sha) per role, canonical authoritative repos only), and revert-commit count. Powers the /community hero strip.	No	Yes	No	Yes
`cross_reference`What relates to one stored item, and what happened to it. ref: a Message-ID or message URL, a commit SHA or URL, a docs URL or page.html, a wiki URL or title, a commitfest URL, CVE-YYYY-NNNNN, or feature:<words> (matched to commitfest titles and to the subjects of the postgres commits that introduce it; ref.entries_used and ref.commits_used say which; a name nothing matches gives empty results, not an error). Returns related threads, commits (with releases and reverted_by), docs, wiki pages, commitfest entries and people, each with why, strongest first: explicit links, shared identifiers, then similar topic. For a postgres commit, thread, entry or feature, timeline says which release shipped it and whether it was reverted or back-patched: status plus dated events (first post, commitfest listings, commits with branch and first release, reverts), each with its source url. kinds narrows; limit_per_kind (default 5, max 25). ~3 s budget: late parts go in timed_out. For feature:<words> and commitfest entries, graph lists the stored design-history features (status, the one release it shipped in, decisions, positions), each fact with confidence, source and evidence; "probably" below 0.8, facts below 0.5 left out. Same as GET /api/v2/related.	What relates to one stored item, and what happened to it. ref: a Message-ID or message URL, a commit SHA or URL, a docs URL or page.html, a wiki URL or title, a commitfest URL, CVE-YYYY-NNNNN, or feature:<words> (matched to commitfest titles and to the subjects of the postgres commits that introduce it; ref.entries_used and ref.commits_used say which; a name nothing matches gives empty results, not an error). Returns related threads, commits (with releases and reverted_by), docs, wiki pages, commitfest entries and people, each with why, strongest first: explicit links, shared identifiers, then similar topic. For a postgres commit, thread, entry or feature, timeline says which release shipped it and whether it was reverted or back-patched: status plus dated events (first post, commitfest listings, commits with branch and first release, reverts), each with its source url. kinds narrows; limit_per_kind (default 5, max 25). ~3 s budget: late parts go in timed_out. For feature:<words> and commitfest entries, graph lists the stored design-history features (status, the one release it shipped in, decisions, positions), each fact with confidence, source and evidence; "probably" below 0.8, facts below 0.5 left out. Same as GET /api/v2/related.	No	Yes	Yes	No
`detect_changes`Detect which symbols changed between two commits by comparing file content hashes.	Detect which symbols changed between two commits by comparing file content hashes.	No	Yes	No	Yes
`discussion_links`Discussion / Closes / Fixes / Backpatch-through trailers attached to one commit. Returns the raw trailer text and any URL extracted. For the messages those links resolve to, plus the committers announcement and messages citing the SHA, use git_search (mail_refs on each result).	Discussion / Closes / Fixes / Backpatch-through trailers attached to one commit. Returns the raw trailer text and any URL extracted. For the messages those links resolve to, plus the committers announcement and messages citing the SHA, use git_search (mail_refs on each result).	No	Yes	No	Yes
`embedding_status`Get embedding coverage statistics: how many messages have embeddings, which model was used, and when embeddings were last generated.	Get embedding coverage statistics: how many messages have embeddings, which model was used, and when embeddings were last generated.	No	Yes	No	Yes
`entry_branches`Repository branches tracked for a commitfest entry. Joins commitfest.entry_repos with ag_repositories so callers see repo name + branch_name + is_authoritative.	Repository branches tracked for a commitfest entry. Joins commitfest.entry_repos with ag_repositories so callers see repo name + branch_name + is_authoritative.	No	Yes	No	Yes
`entry_history`Status changes for a commitfest entry across commitfests. The relational table doesn't carry an audit log, so we approximate the patch's lifeline by joining on shared :entry/thread-message-id (precise) and falling back to title-prefix substring (weak).	Status changes for a commitfest entry across commitfests. The relational table doesn't carry an audit log, so we approximate the patch's lifeline by joining on shared :entry/thread-message-id (precise) and falling back to title-prefix substring (weak).	No	Yes	No	Yes
`find_breaks`Animals that failed on a branch within the time window bounded by two commit SHAs. The window is defined by the earliest started_at observed for either SHA on that branch — not by git topological order, since the buildfarm tables don't carry commit ordering.	Animals that failed on a branch within the time window bounded by two commit SHAs. The window is defined by the earliest started_at observed for either SHA on that branch — not by git topological order, since the buildfarm tables don't carry commit ordering.	No	Yes	No	Yes
`find_contributions`Find raw contribution rows for one person: git commit SHAs / buildfarm animals tagged with a role + release. Useful for drill-down on a contributor's recent work.	Find raw contribution rows for one person: git commit SHAs / buildfarm animals tagged with a role + release. Useful for drill-down on a contributor's recent work.	No	Yes	No	Yes
`find_dead_code`Find functions/methods with zero incoming call graph edges (potentially unused code).	Find functions/methods with zero incoming call graph edges (potentially unused code).	No	Yes	No	Yes
`find_entries_for_author`Find commitfest entries where the given person is an author. Looks up by email (exact) or by name (substring, case-sensitive).	Find commitfest entries where the given person is an author. Looks up by email (exact) or by name (substring, case-sensitive).	No	Yes	No	Yes
`find_entries_for_thread`Find commitfest entries linked to a pgsql-hackers thread by Message-ID. Resolves any Message-ID in the thread to the entries whose commitfest page links it.	Find commitfest entries linked to a pgsql-hackers thread by Message-ID. Resolves any Message-ID in the thread to the entries whose commitfest page links it.	No	Yes	No	Yes
`find_entries_with_failures_on`Cross-domain feed: recent failed buildfarm runs for a named animal, plus commitfest entries with cfbot :failing rollups whose tracked branches overlap the animal's. Note: buildfarm runs commit SHAs and cfbot runs cf/<id> branches, so this verb correlates by branch overlap and time window — not by direct schema join.	Cross-domain feed: recent failed buildfarm runs for a named animal, plus commitfest entries with cfbot :failing rollups whose tracked branches overlap the animal's. Note: buildfarm runs commit SHAs and cfbot runs cf/<id> branches, so this verb correlates by branch overlap and time window — not by direct schema join.	No	Yes	No	Yes
`find_failing_patches`Commitfest entries whose latest cfbot build fails on at least one platform: cf_id, title, entry_status and commitfest_number. entry_status filters (default the active reviewable statuses, e.g. needs-review, ready-for-committer); platform narrows to one CI platform; limit caps the list. Cite https://commitfest.postgresql.org/patch/<cf_id>/.	Commitfest entries whose latest cfbot build fails on at least one platform: cf_id, title, entry_status and commitfest_number. entry_status filters (default the active reviewable statuses, e.g. needs-review, ready-for-committer); platform narrows to one CI platform; limit caps the list. Cite https://commitfest.postgresql.org/patch/<cf_id>/.	No	Yes	No	Yes
`find_failing_runs`Most recent failing buildfarm runs across the entire fleet. Filterable by branch and start cutoff. Use to answer 'what is broken right now?'	Most recent failing buildfarm runs across the entire fleet. Filterable by branch and start cutoff. Use to answer 'what is broken right now?'	No	Yes	No	Yes
`find_passing_long_pending`Green patches stuck in review: entries whose builds pass on every platform yet whose :entry/last-updated is older than N days. Useful for the 'why isn't this committed yet?' question.	Green patches stuck in review: entries whose builds pass on every platform yet whose :entry/last-updated is older than N days. Useful for the 'why isn't this committed yet?' question.	No	Yes	No	Yes
`find_patches_by_platform_status`Patches that pass on some platforms but not others. Example: passing on linux but failing on macos -> portability bug.	Patches that pass on some platforms but not others. Example: passing on linux but failing on macos -> portability bug.	No	Yes	No	Yes
`find_pattern`Search for a regex pattern in code symbol bodies. Uses trigram indexes for acceleration.	Search for a regex pattern in code symbol bodies. Uses trigram indexes for acceleration.	No	Yes	No	Yes
`find_rebase_needed_patches`Entries cfbot reports as no longer applying to master tip (:entry/applies-cleanly is false). These need an author rebase.	Entries cfbot reports as no longer applying to master tip (:entry/applies-cleanly is false). These need an author rebase.	No	Yes	No	Yes
`find_related_discussions`Find mailing list messages related to a commit, topic, or PR. A postgres commit SHA (7-40 hex) returns the mail that refers to that commit (match_mode commit): its Discussion: threads first, then the committers announcement, then messages citing the hash, each with how_it_refers. Anything else searches subject and Message-ID fields via case-insensitive substring; if that returns no hits and an embedding provider is configured, falls back to semantic search across all inboxes.	Find mailing list messages related to a commit, topic, or PR. A postgres commit SHA (7-40 hex) returns the mail that refers to that commit (match_mode commit): its Discussion: threads first, then the committers announcement, then messages citing the hash, each with how_it_refers. Anything else searches subject and Message-ID fields via case-insensitive substring; if that returns no hits and an embedding provider is configured, falls back to semantic search across all inboxes.	No	Yes	No	Yes
`find_similar_messages`Find messages similar to a given message using its embedding vector. Useful for finding related discussions or duplicate threads.	Find messages similar to a given message using its embedding vector. Useful for finding related discussions or duplicate threads.	No	Yes	No	Yes
`find_string_literals`Find occurrences of a literal in current (HEAD) source, restricted to a syntactic kind: "strings" (inside double quotes), "comments" (after // or /*), or "all".	Find occurrences of a literal in current (HEAD) source, restricted to a syntactic kind: "strings" (inside double quotes), "comments" (after // or /*), or "all".	No	Yes	Not declared	Not declared
`get_animal`Profile of one buildfarm animal: hardware/OS/compiler/owner, branches tracked, last build status, plus the last 20 runs (any branch).	Profile of one buildfarm animal: hardware/OS/compiler/owner, branches tracked, last build status, plus the last 20 runs (any branch).	No	Yes	No	Yes
`get_attachment`The whole content of one attachment of a mail message (a patch, a log, a test case), chosen by 1-based index or a filename substring, as listed in get_message/get_thread attachments. Text comes back as text, whatever content type it was sent with (a .patch is ready to read or `git apply`); binary as base64 with encoding=base64. size is the decoded byte count; url downloads the same bytes over HTTP. If your client cuts long tool results, read a large text attachment in pieces with start_line/end_line (at most 2000 lines per call; total_lines and cut say what is left). Cite the message as https://postgr.es/m/<message_id>.	The whole content of one attachment of a mail message (a patch, a log, a test case), chosen by 1-based index or a filename substring, as listed in get_message/get_thread attachments. Text comes back as text, whatever content type it was sent with (a .patch is ready to read or `git apply`); binary as base64 with encoding=base64. size is the decoded byte count; url downloads the same bytes over HTTP. If your client cuts long tool results, read a large text attachment in pieces with start_line/end_line (at most 2000 lines per call; total_lines and cut say what is left). Cite the message as https://postgr.es/m/<message_id>.	No	Yes	No	Yes
`get_author_messages`Find messages by a specific author, optionally filtered by date range. Uses the f: (from) search prefix.	Find messages by a specific author, optionally filtered by date range. Uses the f: (from) search prefix.	No	Yes	No	Yes
`get_callees`Find all symbols that the given symbol calls/references (forward call graph).	Find all symbols that the given symbol calls/references (forward call graph).	No	Yes	No	Yes
`get_callers`Reverse call graph: the symbols that call or reference qualified_name (from search_symbols), each with its file and lines, like `git grep -w <name>` restricted to call sites. HEAD only; macro expansion and function pointers are not followed. limit caps the list. Read a caller with git_show_file at its line.	Reverse call graph: the symbols that call or reference qualified_name (from search_symbols), each with its file and lines, like `git grep -w <name>` restricted to call sites. HEAD only; macro expansion and function pointers are not followed. limit caps the list. Read a caller with git_show_file at its line.	No	Yes	No	Yes
`get_commit`One postgres commit from the code-history index: message, parsed trailers (names only), Discussion threads (links to the archived thread on /m/), back-patch siblings on other branches, first_releases (per branch the change landed on: sha, release such as 14.23, first_version incl. betas, shipped=false when reverted before that release; null release = not yet released), reverted_by and reverts, posted_patch (of the patch mails on its Discussion threads up to its commit date, the one whose changed lines match the commit's best: message_id, date, subject, from, score 0-1, url; null when none shares at least 0.2), files changed with line counts, and its diff rendered from the index (at most 3000 lines; diff_complete says whether it was cut). Accepts a SHA (7+ hex), branch, tag or any version form.	One postgres commit from the code-history index: message, parsed trailers (names only), Discussion threads (links to the archived thread on /m/), back-patch siblings on other branches, first_releases (per branch the change landed on: sha, release such as 14.23, first_version incl. betas, shipped=false when reverted before that release; null release = not yet released), reverted_by and reverts, posted_patch (of the patch mails on its Discussion threads up to its commit date, the one whose changed lines match the commit's best: message_id, date, subject, from, score 0-1, url; null when none shares at least 0.2), files changed with line counts, and its diff rendered from the index (at most 3000 lines; diff_complete says whether it was cut). Accepts a SHA (7+ hex), branch, tag or any version form.	No	Yes	Yes	No
`get_commitfest`Get a single commitfest with entries grouped by status and the top contributors (authors with the most entries).	Get a single commitfest with entries grouped by status and the top contributors (authors with the most entries).	No	Yes	No	Yes
`get_communities`List Louvain community clusters detected in the call graph. Communities group related symbols by functional area.	List Louvain community clusters detected in the call graph. Communities group related symbols by functional area.	No	Yes	No	Yes
`get_community`Get details and member symbols for a specific community.	Get details and member symbols for a specific community.	No	Yes	No	Yes
`get_contributor`A contributor's profile by email (exact) or name (substring): canonical name, page hash, totals and per-release counts by role (authored, reviewed, committed, reported, ...), the 5 latest credited commits (commit_sha = the git SHA, roles = every role they had in it), and buildfarm animals they own. People who hid their page are excluded from name lookups. For what they did recently use whats_new. Cite https://pg.ddx.io/community/<hash>.	A contributor's profile by email (exact) or name (substring): canonical name, page hash, totals and per-release counts by role (authored, reviewed, committed, reported, ...), the 5 latest credited commits (commit_sha = the git SHA, roles = every role they had in it), and buildfarm animals they own. People who hid their page are excluded from name lookups. For what they did recently use whats_new. Cite https://pg.ddx.io/community/<hash>.	No	Yes	No	Yes
`get_contributor_history`Show all past mailing list submissions by a contributor (matched by email address or name).	Show all past mailing list submissions by a contributor (matched by email address or name).	No	Yes	No	Yes
`get_dependents`Get transitive dependents: all symbols in the blast radius if this symbol changes.	Get transitive dependents: all symbols in the blast radius if this symbol changes.	No	Yes	No	Yes
`get_doc_page`One PostgreSQL documentation page as text: path (e.g. "brin.html" or "sql-createtable.html") and optional version ("17", "current"; default the latest). Returns its url, path and stored text (body) with fetched_at. Use search_docs to find the path. Cite the returned url.	One PostgreSQL documentation page as text: path (e.g. "brin.html" or "sql-createtable.html") and optional version ("17", "current"; default the latest). Returns its url, path and stored text (body) with fetched_at. Use search_docs to find the path. Cite the returned url.	No	Yes	No	Yes
`get_entry`One commitfest entry by cf_id (the number in commitfest.postgresql.org/patch/<cf_id>/): title, status, commitfest, authors, reviewers, committer, its mail threads and branches. Read the thread with get_thread; cfbot state with find_failing_patches. Cite https://commitfest.postgresql.org/patch/<cf_id>/.	One commitfest entry by cf_id (the number in commitfest.postgresql.org/patch/<cf_id>/): title, status, commitfest, authors, reviewers, committer, its mail threads and branches. Read the thread with get_thread; cfbot state with find_failing_patches. Cite https://commitfest.postgresql.org/patch/<cf_id>/.	No	Yes	No	Yes
`get_execution_flows`Trace execution flow paths through the call graph from entry points.	Trace execution flow paths through the call graph from entry points.	No	Yes	No	Yes
`get_impact`Analyze the impact of modifying a symbol: risk level, blast radius, affected communities and execution flows.	Analyze the impact of modifying a symbol: risk level, blast radius, affected communities and execution flows.	No	Yes	No	Yes
`get_inbox_info`Get metadata for an inbox (name, addresses, message count, last activity)	Get metadata for an inbox (name, addresses, message count, last activity)	No	Yes	No	Yes
`get_inbox_stats`Return aggregate statistics about an inbox: message counts by time period, top authors, and activity trends.	Return aggregate statistics about an inbox: message counts by time period, top authors, and activity trends.	No	Yes	No	Yes
`get_inbox_summary`Per-inbox summary: total messages, top 10 posters, thread count, date range, and lifetime average messages/day (total messages divided by the days spanned by the archive).	Per-inbox summary: total messages, top 10 posters, thread count, date range, and lifetime average messages/day (total messages divided by the days spanned by the archive).	No	Yes	No	Yes
`get_message`One mail message by Message-ID: headers, in_reply_to/references, decoded body text (by default the author's own words: quoted replies and their attributions, forwarded or Outlook-quoted mail, inline patches, diffstats and the signature removed; full_text=true for everything, quotes included), attachments [{index, filename, content_type, size}] and has_patch. quotes checks citations: each comes back with own_words (in the author's own text, whitespace-normalized) and in_message (anywhere, quoted text included); with include_body=false only the verdicts return. Never raw MIME: get_attachment returns an attachment's content, get_raw_message the RFC 822 source. Finds the list itself unless inbox is given. Cite as https://postgr.es/m/<message_id>.	One mail message by Message-ID: headers, in_reply_to/references, decoded body text (by default the author's own words: quoted replies and their attributions, forwarded or Outlook-quoted mail, inline patches, diffstats and the signature removed; full_text=true for everything, quotes included), attachments [{index, filename, content_type, size}] and has_patch. quotes checks citations: each comes back with own_words (in the author's own text, whitespace-normalized) and in_message (anywhere, quoted text included); with include_body=false only the verdicts return. Never raw MIME: get_attachment returns an attachment's content, get_raw_message the RFC 822 source. Finds the list itself unless inbox is given. Cite as https://postgr.es/m/<message_id>.	No	Yes	No	Yes
`get_message_headers`Get email headers as structured key/value pairs. Returns all headers or a specific header by name.	Get email headers as structured key/value pairs. Returns all headers or a specific header by name.	No	Yes	No	Yes
`get_message_references`Discover cross-references in a message. Returns explicit References/In-Reply-To headers plus any Message-IDs found in the body text, with archive lookup for each.	Discover cross-references in a message. Returns explicit References/In-Reply-To headers plus any Message-IDs found in the body text, with archive lookup for each.	No	Yes	No	Yes
`get_new_messages`Return messages newer than a given article number cursor, enabling agents to poll for new messages without re-scanning. Use after=0 for the first call, then use the returned last_article_num as the cursor for subsequent calls.	Return messages newer than a given article number cursor, enabling agents to poll for new messages without re-scanning. Use after=0 for the first call, then use the returned last_article_num as the cursor for subsequent calls.	No	Yes	No	Yes
`get_ontology`What this server knows and which tool reads it: every kind of fact (person, membership, roster, commitfest entry, feature, decision, position, ...) with its attributes, value types, cardinality, docs and counts, and which kinds refer to which; the design-history graph's relations (thread DISCUSSES feature, decision DECIDES feature, person HOLDS position ABOUT feature, ...), sources (git, commitfest, rule, operator, model) and confidence rules (shown at 0.8 and above, "probably" from 0.5, hidden below; models capped at 0.9); the tables the tools read; and what is loaded (commits, tags, entries). Call it first to learn what can be asked. No arguments. Same as GET /api/v2/ontology.	What this server knows and which tool reads it: every kind of fact (person, membership, roster, commitfest entry, feature, decision, position, ...) with its attributes, value types, cardinality, docs and counts, and which kinds refer to which; the design-history graph's relations (thread DISCUSSES feature, decision DECIDES feature, person HOLDS position ABOUT feature, ...), sources (git, commitfest, rule, operator, model) and confidence rules (shown at 0.8 and above, "probably" from 0.5, hidden below; models capped at 0.9); the tables the tools read; and what is loaded (commits, tags, entries). Call it first to learn what can be asked. No arguments. Same as GET /api/v2/ontology.	No	Yes	Yes	No
`get_patch_branches`Get the git branches created from a patch series. Shows what branches were applied from email patches for code intelligence analysis.	Get the git branches created from a patch series. Shows what branches were applied from email patches for code intelligence analysis.	No	Yes	No	Yes
`get_patch_build_history`Build matrix for one entry: per-platform/config status, log URL, observation time, applies-cleanly flag, rollup.	Build matrix for one entry: per-platform/config status, log URL, observation time, applies-cleanly flag, rollup.	No	Yes	No	Yes
`get_patch_series`Get patch submission history for a forge pull request URL. Returns all iterations submitted to the mailing list.	Get patch submission history for a forge pull request URL. Returns all iterations submitted to the mailing list.	No	Yes	No	Yes
`get_raw_message`Get the complete raw RFC 822 email bytes for a message. Useful for agents that need to parse headers/structure themselves or forward messages.	Get the complete raw RFC 822 email bytes for a message. Useful for agents that need to parse headers/structure themselves or forward messages.	No	Yes	No	Yes
`get_repo_sync_stats`Get commit frequency analysis and sync statistics for a repository. Returns median commit interval, recommended poll frequency, and recent fetch log.	Get commit frequency analysis and sync statistics for a repository. Returns median commit interval, recommended poll frequency, and recent fetch log.	No	Yes	No	Yes
`get_repository_summary`Per-repository summary: total commits, top 10 contributors, branches, language breakdown (from indexed symbols), and a sampled most-touched-paths list.	Per-repository summary: total commits, top 10 contributors, branches, language breakdown (from indexed symbols), and a sampled most-touched-paths list.	No	Yes	No	Yes
`get_signature`Get the function/method signature and doc comment for a symbol.	Get the function/method signature and doc comment for a symbol.	No	Yes	No	Yes
`get_source_info`Detail for a single source by name, the same row list_sources returns. Returns kind, item_count, last_update, next_sync, freshness_status, and description; for a postgresql.org list also poll: the list poller's p_new (probability of mail we lack since its last poll), due, next_poll, factors and the last poll's outcome.	Detail for a single source by name, the same row list_sources returns. Returns kind, item_count, last_update, next_sync, freshness_status, and description; for a postgresql.org list also poll: the list poller's p_new (probability of mail we lack since its last poll), due, next_poll, factors and the last poll's outcome.	No	Yes	No	Yes
`get_symbol`Get full details for a code symbol by its qualified name, including source code, signature, documentation, and file location.	Get full details for a code symbol by its qualified name, including source code, signature, documentation, and file location.	No	Yes	No	Yes
`get_tests_for`Find test symbols that reference the given symbol.	Find test symbols that reference the given symbol.	No	Yes	No	Yes
`get_thread`A mail thread, found by any Message-ID in it, oldest first. Each message: from, to, cc, date, message_id, decoded body text (by default the author's own words: quoted replies, signature and inline patch removed; full_text=true for the whole decoded text; never raw MIME), attachments [{index, filename, content_type, size}] and has_patch. Paged: 20 messages per call (limit max 500; offset/next_offset/has_more); bodies capped at max_body_chars (default 4000; 0 = no cap; body_truncated marks a cut). include_bodies=false gives a cheap outline. Finds the list itself unless inbox is given. Cite as https://postgr.es/m/<message_id>.	A mail thread, found by any Message-ID in it, oldest first. Each message: from, to, cc, date, message_id, decoded body text (by default the author's own words: quoted replies, signature and inline patch removed; full_text=true for the whole decoded text; never raw MIME), attachments [{index, filename, content_type, size}] and has_patch. Paged: 20 messages per call (limit max 500; offset/next_offset/has_more); bodies capped at max_body_chars (default 4000; 0 = no cap; body_truncated marks a cut). include_bodies=false gives a cheap outline. Finds the list itself unless inbox is given. Cite as https://postgr.es/m/<message_id>.	No	Yes	No	Yes
`get_thread_references`Cross-reference graph for an entire thread. Collects all Message-IDs referenced in body text across all messages in the thread and resolves which other threads they point to.	Cross-reference graph for an entire thread. Collects all Message-IDs referenced in body text across all messages in the thread and resolves which other threads they point to.	No	Yes	No	Yes
`get_wiki_history`Get revision history for a wiki page.	Get revision history for a wiki page.	No	Yes	No	Yes
`get_wiki_page`One wiki.postgresql.org page by title: its latest revision content with author and date. Titles are as on the wiki ("Don't Do This", "Todo"). Use search_wiki to find a title, get_wiki_history for older revisions. Cite https://wiki.postgresql.org/wiki/<title>.	One wiki.postgresql.org page by title: its latest revision content with author and date. Titles are as on the wiki ("Don't Do This", "Todo"). Use search_wiki to find a title, get_wiki_history for older revisions. Cite https://wiki.postgresql.org/wiki/<title>.	No	Yes	No	Yes
`git_analyze_activity`Show commit activity over time, bucketed by period. Useful for understanding development pace and trends.	Show commit activity over time, bucketed by period. Useful for understanding development pace and trends.	No	Yes	No	Yes
`git_analyze_authors`Get commit statistics per author: total commits, first and last commit dates. Ranked by commit count.	Get commit statistics per author: total commits, first and last commit dates. Ranked by commit count.	No	Yes	No	Yes
`git_analyze_bus_factor`Identify files with the fewest distinct authors (bus factor risk). Files modified by only one person are knowledge silos.	Identify files with the fewest distinct authors (bus factor risk). Files modified by only one person are knowledge silos.	No	Yes	No	Yes
`git_analyze_churn`Identify the most frequently modified files in the repository. High-churn files may indicate hotspots or unstable code.	Identify the most frequently modified files in the repository. High-churn files may indicate hotspots or unstable code.	No	Yes	No	Yes
`git_analyze_coupling`Find files that are frequently changed together. Logical coupling can reveal hidden dependencies between components.	Find files that are frequently changed together. Logical coupling can reveal hidden dependencies between components.	No	Yes	No	Yes
`git_analyze_hotspots`Aggregate file churn by directory to find the most actively changed areas of the codebase.	Aggregate file churn by directory to find the most actively changed areas of the codebase.	No	Yes	No	Yes
`git_blame`File version history, not a per-line blame: the commits that changed a file on the history of a commit (like `git log <rev> -- <path>`), newest first, each with sha, commit_id, author, date, summary and status (added/modified/deleted). Renames are not followed. Up to `limit` commits (default 100, max 1000); has_more says there are older ones.	File version history, not a per-line blame: the commits that changed a file on the history of a commit (like `git log <rev> -- <path>`), newest first, each with sha, commit_id, author, date, summary and status (added/modified/deleted). Renames are not followed. Up to `limit` commits (default 100, max 1000); has_more says there are older ones.	No	Yes	No	Yes
`git_diff`Two modes: (1) commit-range mode — pass base_branch and head_branch to get the list of commits unique to head_branch (set difference base..head), optionally filtered by author/message/path; (2) content-diff mode — pass from_commit and to_commit to compute file-level unified diffs between two specific commits.	Two modes: (1) commit-range mode — pass base_branch and head_branch to get the list of commits unique to head_branch (set difference base..head), optionally filtered by author/message/path; (2) content-diff mode — pass from_commit and to_commit to compute file-level unified diffs between two specific commits.	No	Yes	No	Yes
`git_log`Commit history like `git log`, newest first, filtered by path (commits touching a file), author (substring), since/until (YYYY-MM-DD or RFC 3339) and branch (any branch, tag or major version such as 17 or 9.6; default the indexed default branch). Each commit: sha (40-hex, cite it), commit_id, message (subject for a branch log), author and dates. limit default 50, max 200; offset pages; has_more. repository defaults to postgres.	Commit history like `git log`, newest first, filtered by path (commits touching a file), author (substring), since/until (YYYY-MM-DD or RFC 3339) and branch (any branch, tag or major version such as 17 or 9.6; default the indexed default branch). Each commit: sha (40-hex, cite it), commit_id, message (subject for a branch log), author and dates. limit default 50, max 200; offset pages; has_more. repository defaults to postgres.	No	Yes	No	Yes
`git_search`Search postgres commit messages (or file paths with search_in=paths) by keywords, newest first (all words must appear, case-insensitive; like `git log -i --grep` with every word). Each commit: sha (40-hex, cite it), commit_id, message, author, date, people credited, and mail_refs: up to 5 messages that refer to it {inbox, message_id, subject, url, how_it_refers: discussion-trailer, committers-announcement or mentions-hash}. repository defaults to postgres; limit default 50, max 200. Details with commit_history. A query that is one SHA or a 7+ char prefix (any case) returns that commit.	Search postgres commit messages (or file paths with search_in=paths) by keywords, newest first (all words must appear, case-insensitive; like `git log -i --grep` with every word). Each commit: sha (40-hex, cite it), commit_id, message, author, date, people credited, and mail_refs: up to 5 messages that refer to it {inbox, message_id, subject, url, how_it_refers: discussion-trailer, committers-announcement or mentions-hash}. repository defaults to postgres; limit default 50, max 200. Details with commit_history. A query that is one SHA or a 7+ char prefix (any case) returns that commit.	No	Yes	No	Yes
`git_show_file`Read a file at any commit, branch, tag or major version (like `git show <rev>:<path>`), from the git clone. commit takes a SHA (>= 7 hex), branch, tag, 17 or 9.6, <ref>~N or a commit_id; default HEAD; an unknown name or path is an error, never a silent HEAD. Returns at most 2000 lines per call: start_line/end_line pick the range, total_lines gives the length and cut=true says more follow. Lines are numbered with a tab (numbered=false gives the exact bytes). Each result has sha (cite it with the path and lines) and ref. Binary files return a note instead of content.	Read a file at any commit, branch, tag or major version (like `git show <rev>:<path>`), from the git clone. commit takes a SHA (>= 7 hex), branch, tag, 17 or 9.6, <ref>~N or a commit_id; default HEAD; an unknown name or path is an error, never a silent HEAD. Returns at most 2000 lines per call: start_line/end_line pick the range, total_lines gives the length and cut=true says more follow. Lines are numbered with a tab (numbered=false gives the exact bytes). Each result has sha (cite it with the path and lines) and ref. Binary files return a note instead of content.	No	Yes	No	Yes
`grep_repository`Literal-text search of the CURRENT source only (HEAD of master for postgres, the default branch elsewhere), like `git grep -F` (regex characters are escaped; case_insensitive=true for -i). Returns up to max_results files (default 50, max 500), each with repo_name, file_path, line_no and snippet (its first matching line). For any other commit, branch, tag, major version or date, for every match with context, or to search history, use code_search (version=, history=). Read a hit with read_file or git_show_file; cite path:line with the sha.	Literal-text search of the CURRENT source only (HEAD of master for postgres, the default branch elsewhere), like `git grep -F` (regex characters are escaped; case_insensitive=true for -i). Returns up to max_results files (default 50, max 500), each with repo_name, file_path, line_no and snippet (its first matching line). For any other commit, branch, tag, major version or date, for every match with context, or to search history, use code_search (version=, history=). Read a hit with read_file or git_show_file; cite path:line with the sha.	No	Yes	Not declared	Not declared
`history-of`One-shot historical context for CI: given content (a diff, file path, symbol, commit subject, or feature name), return the most relevant default-branch commits, the associated mailing-list discussion (message links), and the tracked people involved (community page links). Read-only; composes git history + list search.	One-shot historical context for CI: given content (a diff, file path, symbol, commit subject, or feature name), return the most relevant default-branch commits, the associated mailing-list discussion (message links), and the tracked people involved (community page links). Read-only; composes git history + list search.	No	Yes	Yes	Yes
`hybrid_search`Mailing-list search, keyword (BM25 over the authors' own words) and semantic (embeddings) blended per thread, over every list unless inbox names one or more. Returns up to limit threads (default 20, max 50), best first, each its best message: inbox, message_id, subject, from, date, thread_id, fused_score (0-1), similarity and a short excerpt of the author's own words. Like a ranked `git log --grep` for mail. Cite as https://postgr.es/m/<message_id>; read with get_thread or get_message (inbox from the result). author, since and until restrict both arms to one sender and a date window. Takes search's operators. Echoes operators applied, warnings for dropped ones, skipped if mail is excluded; a query that cannot run is an error. complete=false when the keyword arm ran out of budget_ms or a total is a lower bound. A query that is one commit's SHA (7-40 hex) returns the mail that refers to it (Discussion: thread, committers announcement, mail citing the hash; how_it_refers on each) and commit.	Mailing-list search, keyword (BM25 over the authors' own words) and semantic (embeddings) blended per thread, over every list unless inbox names one or more. Returns up to limit threads (default 20, max 50), best first, each its best message: inbox, message_id, subject, from, date, thread_id, fused_score (0-1), similarity and a short excerpt of the author's own words. Like a ranked `git log --grep` for mail. Cite as https://postgr.es/m/<message_id>; read with get_thread or get_message (inbox from the result). author, since and until restrict both arms to one sender and a date window. Takes search's operators. Echoes operators applied, warnings for dropped ones, skipped if mail is excluded; a query that cannot run is an error. complete=false when the keyword arm ran out of budget_ms or a total is a lower bound. A query that is one commit's SHA (7-40 hex) returns the mail that refers to it (Discussion: thread, committers announcement, mail citing the hash; how_it_refers on each) and commit.	No	Yes	No	Yes
`hybrid_search_code`Combined keyword + semantic code search using Reciprocal Rank Fusion. Requires embeddings to be generated.	Combined keyword + semantic code search using Reciprocal Rank Fusion. Requires embeddings to be generated.	No	Yes	No	Yes
`list_animals`List PostgreSQL buildfarm animals. Filterable by OS, branch tracked, last build status, or owner. Failing animals are returned first (sort key: last_status='failed' DESC, name ASC).	List PostgreSQL buildfarm animals. Filterable by OS, branch tracked, last build status, or owner. Failing animals are returned first (sort key: last_status='failed' DESC, name ASC).	No	Yes	No	Yes
`list_branches`List tracked branches for a repository, including head commit and default branch status.	List tracked branches for a repository, including head commit and default branch status.	No	Yes	No	Yes
`list_commitfests`List PostgreSQL commitfests indexed in the mentat triple store. Each commitfest carries a status (:open / :in-progress / :closed) and an entry count grouped by status.	List PostgreSQL commitfests indexed in the mentat triple store. Each commitfest carries a status (:open / :in-progress / :closed) and an entry count grouped by status.	No	Yes	No	Yes
`list_contributors`List PostgreSQL community contributors aggregated across git trailers (Reviewed-by, Tested-by, etc.), commit author/committer headers, and buildfarm animal owners. Sorted by total contributions descending. Filterable by release / role / source.	List PostgreSQL community contributors aggregated across git trailers (Reviewed-by, Tested-by, etc.), commit author/committer headers, and buildfarm animal owners. Sorted by total contributions descending. Filterable by release / role / source.	No	Yes	No	Yes
`list_discord_channels`List monitored Discord channels with message counts.	List monitored Discord channels with message counts.	No	Yes	No	Yes
`list_doc_versions`List available documentation versions with page counts.	List available documentation versions with page counts.	No	Yes	No	Yes
`list_entries`List commitfest entries (proposed patch series). Filterable by status, commitfest number, or topic; paginated.	List commitfest entries (proposed patch series). Filterable by status, commitfest number, or topic; paginated.	No	Yes	No	Yes
`list_files`List the files of the postgres source under a directory at any commit, branch, tag or date (code-history index), with line counts; depth folds deeper paths into directories with file counts; glob filters paths.	List the files of the postgres source under a directory at any commit, branch, tag or date (code-history index), with line counts; depth folds deeper paths into directories with file counts; glob filters paths.	No	Yes	Yes	No
`list_inboxes`List all configured agora mailboxes with name, message_count, latest_message_date, latest_import_date, listid (when known) and description. Optional min_messages filter; limit/offset are accepted for forward compatibility.	List all configured agora mailboxes with name, message_count, latest_message_date, latest_import_date, listid (when known) and description. Optional min_messages filter; limit/offset are accepted for forward compatibility.	No	Yes	No	Yes
`list_projects`List bridge-configured projects linking a forge repository to a mailing list inbox.	List bridge-configured projects linking a forge repository to a mailing list inbox.	No	Yes	No	Yes
`list_recent`List recent messages from an inbox	List recent messages from an inbox	No	Yes	No	Yes
`list_repositories`List all registered git repositories with name, branch, commit_count, file_count, indexed-symbol_count, latest_commit, last_fetched_at, and import_state. Optional min_commits and branch filters; limit/offset accepted for forward compatibility.	List all registered git repositories with name, branch, commit_count, file_count, indexed-symbol_count, latest_commit, last_fetched_at, and import_state. Optional min_commits and branch filters; limit/offset accepted for forward compatibility.	No	Yes	No	Yes
`list_sources`Every source behind this server with its kind (inbox, repository, docs, wiki, discord), item count, last update and freshness (fresh/stale): the 85 mailing lists, the git repositories, the documentation releases, the wiki and Discord. Use it to learn the inbox and repository names other tools accept and how current each is. kind filters; min_items drops small sources.	Every source behind this server with its kind (inbox, repository, docs, wiki, discord), item count, last update and freshness (fresh/stale): the 85 mailing lists, the git repositories, the documentation releases, the wiki and Discord. Use it to learn the inbox and repository names other tools accept and how current each is. kind filters; min_items drops small sources.	No	Yes	No	Yes
`list_threads`Browse recent threads (topic-level view). Returns thread summaries with message counts, date ranges, and latest message metadata.	Browse recent threads (topic-level view). Returns thread summaries with message counts, date ranges, and latest message metadata.	No	Yes	No	Yes
`read_file`Read a file of the postgres source at any commit, branch, tag or date from the code-history index: numbered lines, at most 2000 per call (page with start_line/end_line), byte-exact to git. Says total_lines and complete; binary files return their metadata only.	Read a file of the postgres source at any commit, branch, tag or date from the code-history index: numbered lines, at most 2000 per call (page with start_line/end_line), byte-exact to git. Says total_lines and complete; binary files return their metadata only.	No	Yes	Yes	No
`recent_commitfest_activity`Rolling window of commitfest entries updated in the last N days. Returns the entries plus a status histogram. Uses the relational commitfest.entries table for predictable latency.	Rolling window of commitfest entries updated in the last N days. Returns the entries plus a status histogram. Uses the relational commitfest.entries table for predictable latency.	No	Yes	No	Yes
`regex_search_code`Regular-expression search of the CURRENT source only (HEAD of master for postgres, the default branch elsewhere), like `git grep -E` with grep's line semantics: ^ and $ anchor at line starts and ends, . does not cross lines. PostgreSQL regex syntax (\s, \w, (?i) work). path_glob narrows by SQL LIKE pattern ("src/backend/%.c"), repository by name. Returns up to max_results files (default 50, max 500) with repo_name, file_path, line_no and snippet (its first matching line). For any other commit, branch, tag, major version or date, all matches with context, or history, use code_search with match=regex. Cite path:line with the sha.	Regular-expression search of the CURRENT source only (HEAD of master for postgres, the default branch elsewhere), like `git grep -E` with grep's line semantics: ^ and $ anchor at line starts and ends, . does not cross lines. PostgreSQL regex syntax (\s, \w, (?i) work). path_glob narrows by SQL LIKE pattern ("src/backend/%.c"), repository by name. Returns up to max_results files (default 50, max 500) with repo_name, file_path, line_no and snippet (its first matching line). For any other commit, branch, tag, major version or date, all matches with context, or history, use code_search with match=regex. Cite path:line with the sha.	No	Yes	Not declared	Not declared
`release_contributors`Top contributors per role for one release. Scope: canonical authoritative repos only (ag_repositories.is_authoritative = TRUE). Returns top 20 per role across authored / reviewed / tested / reported / committed (per-role distinct-commit counts).	Top contributors per role for one release. Scope: canonical authoritative repos only (ag_repositories.is_authoritative = TRUE). Returns top 20 per role across authored / reviewed / tested / reported / committed (per-role distinct-commit counts).	No	Yes	No	Yes
`repository_stats`Get detailed statistics for a git repository including commit count, file count, branch, and import state.	Get detailed statistics for a git repository including commit count, file count, branch, and import state.	No	Yes	No	Yes
`retrieve_context`START HERE for a question about PostgreSQL. Searches every mailing list (inbox narrows it) with hybrid keyword + semantic ranking and returns cited passages that fit token_budget (default 4000, max 32000): one passage per thread, each the author's own words (quotes, signature and patch removed, cut at ~1200 chars) with url, inbox, message_id, from and date. found=false with a reason when the archive does not appear to discuss the question, instead of weak matches. Retrieval only: write the answer yourself. Cite each claim with its passage url or https://postgr.es/m/<message_id>; open a thread with get_thread. author, since and until restrict it to what one person wrote in a date window (filter echoes them). The question may carry search operators (after:2020, site:<list>); operators, warnings and skipped report what they did. complete=false when the search ran out of budget_ms. A commit SHA (7-40 hex) as the question returns the passages of the mail that refers to that commit, and commit.	START HERE for a question about PostgreSQL. Searches every mailing list (inbox narrows it) with hybrid keyword + semantic ranking and returns cited passages that fit token_budget (default 4000, max 32000): one passage per thread, each the author's own words (quotes, signature and patch removed, cut at ~1200 chars) with url, inbox, message_id, from and date. found=false with a reason when the archive does not appear to discuss the question, instead of weak matches. Retrieval only: write the answer yourself. Cite each claim with its passage url or https://postgr.es/m/<message_id>; open a thread with get_thread. author, since and until restrict it to what one person wrote in a date window (filter echoes them). The question may carry search operators (after:2020, site:<list>); operators, warnings and skipped report what they did. complete=false when the search ran out of budget_ms. A commit SHA (7-40 hex) as the question returns the passages of the mail that refers to that commit, and commit.	No	Yes	Yes	Yes
`search`Keyword search of mailing-list messages (BM25 over subject, sender and the authors' own words), every list unless inbox narrows it. Operators in query: s:/intitle: subject, f:/from: sender, b:/intext: body, after:/before:/d:2024-01..2025-01 dates, site:<list>, filetype:patch, link:<url glob>, /regex/. Returns messages best first (limit default 50, max 200; offset pages; collapse_threads=true keeps one per thread), each with inbox, message_id, subject, from, date, thread_id and an excerpt, plus total and has_more. Use it for exact words, names and identifiers; hybrid_search for questions. Cite as https://postgr.es/m/<message_id>. author, since and until restrict it to one sender and a date window. Echoes operators applied, warnings for dropped ones, skipped if mail is excluded; a query that cannot run is an error. complete=false when it ran out of budget_ms or total is a lower bound (timed_out, total_partial, total_capped say which). With define:<term> it also returns definition, the same card search_docs returns. A query that is one commit's SHA (7-40 hex) returns the mail that refers to it (how_it_refers on each) and commit.	Keyword search of mailing-list messages (BM25 over subject, sender and the authors' own words), every list unless inbox narrows it. Operators in query: s:/intitle: subject, f:/from: sender, b:/intext: body, after:/before:/d:2024-01..2025-01 dates, site:<list>, filetype:patch, link:<url glob>, /regex/. Returns messages best first (limit default 50, max 200; offset pages; collapse_threads=true keeps one per thread), each with inbox, message_id, subject, from, date, thread_id and an excerpt, plus total and has_more. Use it for exact words, names and identifiers; hybrid_search for questions. Cite as https://postgr.es/m/<message_id>. author, since and until restrict it to one sender and a date window. Echoes operators applied, warnings for dropped ones, skipped if mail is excluded; a query that cannot run is an error. complete=false when it ran out of budget_ms or total is a lower bound (timed_out, total_partial, total_capped say which). With define:<term> it also returns definition, the same card search_docs returns. A query that is one commit's SHA (7-40 hex) returns the mail that refers to it (how_it_refers on each) and commit.	No	Yes	No	Yes
`search_all_sources`Unified search across all document sources (docs, wiki, and email). Returns results ranked by relevance. Search operators (site:, after:, before:, from:, link:, /regex/ ...) are applied per source; operators and warnings say what the query used, and skipped names each source the query left out and why. With define:<term> it also returns definition, the same card search_docs returns.	Unified search across all document sources (docs, wiki, and email). Returns results ranked by relevance. Search operators (site:, after:, before:, from:, link:, /regex/ ...) are applied per source; operators and warnings say what the query used, and skipped names each source the query left out and why. With define:<term> it also returns definition, the same card search_docs returns.	No	Yes	No	Yes
`search_commitfest`Full-text search of commitfest entries (title first, then author/reviewer/committer names), in the current commitfest by default, or commitfests="all" (back to 2014) or a comma list of numbers. Websearch syntax: "phrase", -term, or. Each result: cf_id, title, status, commitfest(s), people, last update, the commitfest.postgresql.org patch url and the pg.ddx.io thread link. limit default 20, max 50. Details with get_entry; cite the patch url. Search operators apply (intitle:, from:, after:/before:, /regex/, commitfest:, release:); operators, warnings and skipped report them. Each result carries outlook: the commit model's estimate (p_cf, p_release, bands low/medium/high, health), or null. A commit SHA (7-40 hex) as the query returns the entries tied to its Discussion: threads, in every commitfest, and commit.	Full-text search of commitfest entries (title first, then author/reviewer/committer names), in the current commitfest by default, or commitfests="all" (back to 2014) or a comma list of numbers. Websearch syntax: "phrase", -term, or. Each result: cf_id, title, status, commitfest(s), people, last update, the commitfest.postgresql.org patch url and the pg.ddx.io thread link. limit default 20, max 50. Details with get_entry; cite the patch url. Search operators apply (intitle:, from:, after:/before:, /regex/, commitfest:, release:); operators, warnings and skipped report them. Each result carries outlook: the commit model's estimate (p_cf, p_release, bands low/medium/high, health), or null. A commit SHA (7-40 hex) as the query returns the entries tied to its Discussion: threads, in every commitfest, and commit.	No	Yes	No	Yes
`search_commits`Search postgres commits (code-history index), newest first, like git log: range (a rev, or A..B; default the newest release branch), message (regex, case-insensitive), author (regex over author, committer and Author/Co-authored-by/Reviewed-by trailers), paths, since/until (YYYY-MM-DD), changed_lines (a regex an added or removed line matches, as git log -G) and occurrences (a string whose count in a file changed, as git log -S). complete=false when changed_lines/occurrences matched more lines than it reads (300,000): commits may be missing.	Search postgres commits (code-history index), newest first, like git log: range (a rev, or A..B; default the newest release branch), message (regex, case-insensitive), author (regex over author, committer and Author/Co-authored-by/Reviewed-by trailers), paths, since/until (YYYY-MM-DD), changed_lines (a regex an added or removed line matches, as git log -G) and occurrences (a string whose count in a file changed, as git log -S). complete=false when changed_lines/occurrences matched more lines than it reads (300,000): commits may be missing.	No	Yes	Yes	No
`search_discord_topics`Find PostgreSQL Discord discussions semantically related to a query. Returns only the channel, approximate date range, and participants of relevant conversations — never message content or links (per the Discord community agreement).	Find PostgreSQL Discord discussions semantically related to a query. Returns only the channel, approximate date range, and participants of relevant conversations — never message content or links (per the Discord community agreement).	No	Yes	No	Yes
`search_docs`Full-text search of the PostgreSQL documentation (websearch syntax: "phrase", -term, or), title matches first. Searches the current release unless version (one, e.g. "17") or versions (several) is given; a page matching in several selected versions is one result listing each version and its URL. Returns title, path, url, the versions it matched and a snippet. With define:<term> in query (define:MVCC, define:"write-ahead log", define:T611, define:LATERAL) it also returns definition: the PostgreSQL glossary entry, SQL standard feature or SQL key word for the term, as paragraphs of text segments whose links point at other terms, docs sections and features. Read a page with get_doc_page; cite its postgresql.org/docs url. Search operators apply (intitle:, inurl:, after:/before: pick the versions current then); operators, warnings and skipped report them.	Full-text search of the PostgreSQL documentation (websearch syntax: "phrase", -term, or), title matches first. Searches the current release unless version (one, e.g. "17") or versions (several) is given; a page matching in several selected versions is one result listing each version and its URL. Returns title, path, url, the versions it matched and a snippet. With define:<term> in query (define:MVCC, define:"write-ahead log", define:T611, define:LATERAL) it also returns definition: the PostgreSQL glossary entry, SQL standard feature or SQL key word for the term, as paragraphs of text segments whose links point at other terms, docs sections and features. Read a page with get_doc_page; cite its postgresql.org/docs url. Search operators apply (intitle:, inurl:, after:/before: pick the versions current then); operators, warnings and skipped report them.	No	Yes	No	Yes
`search_patches`Find patch series by parsing [PATCH v2 3/7]-style subject prefixes. Returns structured patch metadata including version, sequence, total, and series grouping. complete=false when it ran out of budget_ms.	Find patch series by parsing [PATCH v2 3/7]-style subject prefixes. Returns structured patch metadata including version, sequence, total, and series grouping. complete=false when it ran out of budget_ms.	No	Yes	No	Yes
`search_symbols`Find C functions, macros, types and variables by name in the indexed source (HEAD): BM25 on names, then fuzzy and body matches. Filter by kind (function, struct, macro, ...), language, repository. Each result: qualified_name, name, kind, language, file, start_line and end_line. Like `ctags`/`git grep -w` for definitions. Follow with get_callers, or git_show_file with start_line/end_line to read the body.	Find C functions, macros, types and variables by name in the indexed source (HEAD): BM25 on names, then fuzzy and body matches. Filter by kind (function, struct, macro, ...), language, repository. Each result: qualified_name, name, kind, language, file, start_line and end_line. Like `ctags`/`git grep -w` for definitions. Follow with get_callers, or git_show_file with start_line/end_line to read the body.	No	Yes	No	Yes
`search_wiki`Full-text search (websearch syntax) of wiki.postgresql.org. By default searches each page's current text; history=true searches every revision and returns, per page, the latest matching revision (rev_id, revision_url, author, comment, timestamp, is_current) and how many matched; since/until bound the revision dates. Read a page with get_wiki_page; cite its wiki url. Search operators apply (intitle:, from:, after:/before:, link:, /regex/); operators, warnings and skipped report them. A commit SHA (7-40 hex) as the query returns the pages whose current text cites it, and commit.	Full-text search (websearch syntax) of wiki.postgresql.org. By default searches each page's current text; history=true searches every revision and returns, per page, the latest matching revision (rev_id, revision_url, author, comment, timestamp, is_current) and how many matched; since/until bound the revision dates. Read a page with get_wiki_page; cite its wiki url. Search operators apply (intitle:, from:, after:/before:, link:, /regex/); operators, warnings and skipped report them. A commit SHA (7-40 hex) as the query returns the pages whose current text cites it, and commit.	No	Yes	No	Yes
`search-regex`Full-text search across mailing list messages using POSIX regex patterns. Supports edit-distance fuzzy matching via the `k` parameter (0 = exact regex, >=1 = up to k insertions/deletions/substitutions per match). Same prefix syntax as `search`: s:subject f:from t:to d:2024-01..2025-01 b:body_text	Full-text search across mailing list messages using POSIX regex patterns. Supports edit-distance fuzzy matching via the `k` parameter (0 = exact regex, >=1 = up to k insertions/deletions/substitutions per match). Same prefix syntax as `search`: s:subject f:from t:to d:2024-01..2025-01 b:body_text	No	Yes	No	Yes
`semantic_search`Search messages on every list (or the lists in inbox) by semantic similarity using vector embeddings; each result names its inbox. Returns messages most similar in meaning to the query text. Requires embeddings to be generated first (see embedding_status). Each result carries an 'excerpt': the author's own words, quoted text and signatures removed.	Search messages on every list (or the lists in inbox) by semantic similarity using vector embeddings; each result names its inbox. Returns messages most similar in meaning to the query text. Requires embeddings to be generated first (see embedding_status). Each result carries an 'excerpt': the author's own words, quoted text and signatures removed.	No	Yes	No	Yes
`semantic_search_code`Search code symbols by semantic similarity using vector embeddings. Requires embeddings.	Search code symbols by semantic similarity using vector embeddings. Requires embeddings.	No	Yes	No	Yes
`symbols_in_file`List all code symbols defined in a file, ordered by line number.	List all code symbols defined in a file, ordered by line number.	No	Yes	No	Yes
`upcoming_events`PostgreSQL community events in a date window: conferences, PGDays, meetups, online events, Call for Papers and registration deadlines, conference talks (with speakers and their pg.ddx.io person hash), Talking Postgres episodes, release dates and commitfests. Same data as the iCalendar feeds at https://pg.ddx.io/calendars (community event listings from the PostgreSQL Event Calendar, curated by Andreas Scherbaum).	PostgreSQL community events in a date window: conferences, PGDays, meetups, online events, Call for Papers and registration deadlines, conference talks (with speakers and their pg.ddx.io person hash), Talking Postgres episodes, release dates and commitfests. Same data as the iCalendar feeds at https://pg.ddx.io/calendars (community event listings from the PostgreSQL Event Calendar, curated by Andreas Scherbaum).	No	Yes	Yes	Yes
`whats_new`Catch up: everything a person or group did, and where they were named, in a window, newest first per kind (mail grouped by thread). who: a name (fuzzy; close matches return ambiguous [{name, hash}]), email, hash:<8 hex>, team:<slug>, org:<name>, new:<window>, a phrase ('the core team'), or a list. since/until: ISO date, today, 2w/14d/1m, pg19 (a release's development window), all; default 14 days. during: a calendar event uid/url. topic narrows by hybrid search. Kinds: waiting (one person, no topic: what is on their radar, each with its rule (reply_to_you > called_out > to_cc > named, then commitfest and cfbot rules (Needs review not when they wrote the entry's newest message; cfbot_not_applying_your_patch: cfbot cannot apply the newest patch on an entry and they posted it, whatever their role), then code_changed: open patches changing files they wrote much of on master in threads they have not posted in, group code_changes, with files and their share, score, proposer, patch_url; called_out items carry call_out {evidence, excerpt, confidence, url} quoting the message that asked them to take part), group, priority 0-100 and why, and an outlook (a model's estimate: unit commitfest = P(commit) for the CF and release and thread health, when its thread is in an open commitfest; unit thread = p_commit, P(a commit from a patch thread in no commitfest within horizon_days); people to seek out, factors, model_version)), acted (one person, no topic: what they did about what waited on them: answered, sent_patch, committed, with what asked them and when; an item leaves waiting when they act and shows here), mail_from, mail_to_cc, mail_mention, git_author, git_credit, git_mention, wiki_edit, wiki_mention, commitfest, calendar, roster. waiting mail items also carry p_more_replies (the reply model's P(another message within 60 days), about the thread), p_reply (P(the person posts within 60 days); live items are ordered by it) and reply {factors, cell_n, model_version}; threads it c	Catch up: everything a person or group did, and where they were named, in a window, newest first per kind (mail grouped by thread). who: a name (fuzzy; close matches return ambiguous [{name, hash}]), email, hash:<8 hex>, team:<slug>, org:<name>, new:<window>, a phrase ('the core team'), or a list. since/until: ISO date, today, 2w/14d/1m, pg19 (a release's development window), all; default 14 days. during: a calendar event uid/url. topic narrows by hybrid search. Kinds: waiting (one person, no topic: what is on their radar, each with its rule (reply_to_you > called_out > to_cc > named, then commitfest and cfbot rules (Needs review not when they wrote the entry's newest message; cfbot_not_applying_your_patch: cfbot cannot apply the newest patch on an entry and they posted it, whatever their role), then code_changed: open patches changing files they wrote much of on master in threads they have not posted in, group code_changes, with files and their share, score, proposer, patch_url; called_out items carry call_out {evidence, excerpt, confidence, url} quoting the message that asked them to take part), group, priority 0-100 and why, and an outlook (a model's estimate: unit commitfest = P(commit) for the CF and release and thread health, when its thread is in an open commitfest; unit thread = p_commit, P(a commit from a patch thread in no commitfest within horizon_days); people to seek out, factors, model_version)), acted (one person, no topic: what they did about what waited on them: answered, sent_patch, committed, with what asked them and when; an item leaves waiting when they act and shows here), mail_from, mail_to_cc, mail_mention, git_author, git_credit, git_mention, wiki_edit, wiki_mention, commitfest, calendar, roster. waiting mail items also carry p_more_replies (the reply model's P(another message within 60 days), about the thread), p_reply (P(the person posts within 60 days); live items are ordered by it) and reply {factors, cell_n, model_version}; threads it c	No	Yes	Yes	No

Details

Registry status: Active
Published: Oct 23, 2026
Updated: Oct 23, 2026
Website: https://pg.ddx.io/⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Developer toolsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing