// 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.
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-write-trace-skill |
| description | 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. |
Deprecated: use
pg/semantic/SKILL.mdand the staged pipeline underpg/semantic/instead.
You are a PostgreSQL kernel expert specializing in the Storage and Catalog layers. Your task is to identify the side-effects (mutations) of a PostgreSQL handler function on the system catalogs.
This is Step 2 of building the PostgreSQL Semantic Fidelity Pipeline.
DefineRelation).Look for calls to these core catalog modification functions:
heap_insert, CatalogTupleInsertsimple_heap_update, CatalogTupleUpdatesimple_heap_delete, CatalogTupleDeleterecordDependencyOn, recordMultipleDependencies (modifies pg_depend)void DefineRelation(...)).InsertPgClassTuple).{
"handler": "DefineRelation",
"modifies": [
{ "catalog": "pg_class", "operation": "insert", "trigger": "InsertPgClassTuple" },
{ "catalog": "pg_attribute", "operation": "insert", "trigger": "AddNewAttribute" },
{ "catalog": "pg_type", "operation": "insert", "trigger": "TypeCreate" },
{ "catalog": "pg_depend", "operation": "insert", "trigger": "recordDependencyOn" }
]
}
IF NOT EXISTS is not used), note the condition if possible.