// Traces the PostgreSQL Analyzer (analyze.go/analyze.c) to identify which system catalogs (e.g., pg_operator, pg_type, pg_proc) are queried to resolve a specific SQL statement or semantic element. Use this to identify dependencies.
Maps PostgreSQL parser BNF grammar statements to their corresponding PostgreSQL C source code entry points (e.g., in utility.c). Use this to find which C function handles a specific parsed SQL statement.
Synthesizes the outputs of pg-bnf-source-mapper, pg-write-trace-skill, and pg-read-trace-skill into a master PG_SEMANTIC_INVENTORY.json. It maps statements to regression tests (pg_regress) to provide a complete coverage plan.
Traces the PostgreSQL Analyzer (analyze.go/analyze.c) to identify which system catalogs (e.g., pg_operator, pg_type, pg_proc) are queried to resolve a specific SQL statement or semantic element. Use this to identify dependencies.
Traces PostgreSQL C source code to identify which system catalogs (e.g., pg_class, pg_attribute) are modified (inserted, updated, or deleted) by a specific handler function. Use this to find the side-effects of a DDL statement.
Maps PostgreSQL parser BNF grammar statements to their corresponding PostgreSQL C source code entry points (e.g., in utility.c). Use this to find which C function handles a specific parsed SQL statement.
Synthesizes the outputs of pg-bnf-source-mapper, pg-write-trace-skill, and pg-read-trace-skill into a master PG_SEMANTIC_INVENTORY.json. It maps statements to regression tests (pg_regress) to provide a complete coverage plan.
| name | pg-read-trace-skill |
| description | Traces the PostgreSQL Analyzer (analyze.go/analyze.c) to identify which system catalogs (e.g., pg_operator, pg_type, pg_proc) are queried to resolve a specific SQL statement or semantic element. Use this to identify dependencies. |
Deprecated: use
pg/semantic/SKILL.mdand the staged pipeline underpg/semantic/instead.
You are an expert on the PostgreSQL Analyzer and Semantic Engine. Your task is to identify the read dependencies (lookups) of a PostgreSQL SQL statement or semantic element on the system catalogs.
This is Step 3 of building the PostgreSQL Semantic Fidelity Pipeline.
OpExpr, SelectStmt).pg/catalog/analyze.go and/or src/backend/parser/analyze.c.Look for calls to these core catalog lookup functions:
SearchSysCache, SearchSysCacheCopy, SearchSysCacheListheap_open (on catalog relations)GetRelation, TypeByOID, LookupOperatorExact (in Omni's catalog.go)transform* functions in analyze.c (e.g., transformExpr, transformSelectStmt).OpernameGetOprid).{
"element": "OpExpr",
"reads": [
{ "catalog": "pg_operator", "lookup_key": "opname, left, right", "purpose": "resolve operator" },
{ "catalog": "pg_type", "lookup_key": "oid", "purpose": "check operand compatibility" },
{ "catalog": "pg_cast", "lookup_key": "source, target", "purpose": "resolve implicit casting" }
]
}
analyze.go.