pg_dump
Skill1.1k starsChanged 9 months agoApache-2.0View on GitHub
Consult PostgreSQL's pg_dump implementation for guidance on system catalog queries and schema extraction when implementing pgschema features. Use this skill when adding new schema object support, debugging inspector.go queries, understanding how PostgreSQL represents objects internally, or handling version-specific features across PostgreSQL 14-18.
1 other project uses a version of this.
Trending
More talk lately.about the whole repository
Most recently taken up by
- pgschema/pgschemaword for word, first seen Oct 8, 2026
Who's talking about pgplex/pgschema
- ONREZA/sqlx-js“feat: harden sql contract boundaries”GitHub · Aug 4, 2026 · 1 reactions
- NixOS/nixpkgs“pgschema: 1.13.4 -> 1.14.1”GitHub · Nov 12, 2026
- yuniruyuni/FighterNotes“ci(deps): Update release supply chain”GitHub · Nov 8, 2026
- sudosubin/agents.nix“agent-skills.github.pgplex.pgschema: 1.14.0 → 1.14.1”GitHub · Nov 8, 2026
- sudosubin/agents.nix“agent-skills.github.pgplex.pgschema: 1.13.4 → 1.14.0”GitHub · Nov 6, 2026
The biggest 5 of 22 mentions linking to the repository that our crawl found. Each line is their own headline.
See all 22
Talked about on GitHub (22 times).
On GitHub · 22
- Aug 4, 2026feat: harden sql contract boundaries — ONREZA/sqlx-js1 reaction
- Nov 12, 2026pgschema: 1.13.4 -> 1.14.1 — NixOS/nixpkgs0 reactions · 1 comment
- Nov 8, 2026ci(deps): Update release supply chain — yuniruyuni/FighterNotes0 reactions · 1 comment
- Nov 8, 2026agent-skills.github.pgplex.pgschema: 1.14.0 → 1.14.1 — sudosubin/agents.nix0 reactions
- Nov 6, 2026agent-skills.github.pgplex.pgschema: 1.13.4 → 1.14.0 — sudosubin/agents.nix0 reactions
17 more on GitHub
- Oct 31, 2026pgschema: 1.13.3 -> 1.13.4 — NixOS/nixpkgs0 reactions · 3 comments
- Oct 30, 2026ci(deps): Update release supply chain — yuniruyuni/FighterNotes0 reactions · 2 comments
- Oct 27, 2026agent-skills.github.pgplex.pgschema: 1.13.3 → 1.13.4 — sudosubin/agents.nix0 reactions
- Oct 19, 2026pgschema: 1.13.1 -> 1.13.3 — NixOS/nixpkgs0 reactions · 4 comments
- Oct 15, 2026agent-skills.github.pgplex.pgschema: 1.13.2 → 1.13.3 — sudosubin/agents.nix0 reactions
- Oct 15, 2026agent-skills.github.pgplex.pgschema: 1.13.1 → 1.13.2 — sudosubin/agents.nix0 reactions
- Oct 11, 2026chore(deps): update release supply chain — yuniruyuni/FighterNotes0 reactions · 1 comment
- Oct 1, 2026agent-skills.github.pgplex.pgschema: init at 1.13.1 — sudosubin/agents.nix0 reactions
- Sep 27, 2026pgschema: 1.13.0 -> 1.13.1 — NixOS/nixpkgs0 reactions · 4 comments
- Sep 17, 2026pgschema: 1.12.5 -> 1.13.0 — NixOS/nixpkgs0 reactions · 5 comments
- Sep 6, 2026pgschema: 1.12.4 -> 1.12.5 — NixOS/nixpkgs0 reactions · 4 comments
- Aug 27, 2026pgschema: 1.12.3 -> 1.12.4 — NixOS/nixpkgs0 reactions · 1 comment
- Jun 15, 2026sha256 is inconsistent with the one on github release — pgplex/homebrew-pgschema0 reactions
- Apr 22, 2026pg-delta: add enum-arg function privilege parity coverage (pgschema #366) — supabase/pg-toolbelt0 reactions · 1 comment
- Apr 22, 2026pg-delta: add parity coverage for DEFERRABLE UNIQUE constraints (pgschema #404) — supabase/pg-toolbelt0 reactions · 2 comments
- Mar 5, 2026Daily scan, git submodules, GitHub Models API, Copilot instruction docs — avallete/delta-schema-compare0 reactions
- Mar 3, 2026Joergs TODO list — numtide/llm-agents.nix0 reactions
Other versions1 project uses a version of this.
Word for word · 1
- pgschema/pgschema★ 1.1k100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- fix_bugSkill
- postgres_syntaxSkill
- review_commentsSkill
- run_testsSkill
- validate_dbSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 52
Use pgx parameter binding
- Distinctive: line 54
Add version detection if needed
- Very specific: line 58
Always reference for: system catalog query patterns, correct use of pg_get_* functions, version-specific feature detection, object …
- Very specific: line 62
Don't copy: output formatting (pgschema has different conventions), archive/restore logic, full-database scope (pgschema is …
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
pg_dump Reference
Reference pg_dump's implementation for correct system catalog queries and schema extraction patterns.
Source
Repository: https://github.com/postgres/postgres/blob/master/src/bin/pg_dump/
Key files:
pg_dump.c- Main implementation with all system catalog queriespg_dump.h- Data structurespg_dump_sort.c- Dependency sortingcommon.c- Shared catalog query utilities
Object Type → pg_dump Function → System Catalogs
| Object | Function | Catalogs |
| Tables & Columns | getTables() | pg_class, pg_attribute, pg_type |
| Constraints | getConstraints() | pg_constraint |
| Indexes | getIndexes() | pg_index, pg_class |
| Triggers | getTriggers() | pg_trigger, pg_proc |
| Functions | getFuncs() | pg_proc |
| Views | getViews() | pg_class, pg_rewrite |
| Sequences | getSequences() | pg_sequence, pg_class |
| Policies | getPolicies() | pg_policy |
| Types | getTypes() | pg_type |
| Aggregates | getAggregates() | pg_aggregate, pg_proc |
| Comments | getComments() | pg_description |
Key Helper Functions
pg_get_expr(expr, relation, pretty)- Deparse expressions (defaults, WHEN clauses, index predicates)pg_get_constraintdef(oid, pretty)- Get constraint DDLpg_get_indexdef(oid, column, pretty)- Get index DDLpg_get_triggerdef(oid, pretty)- Get full trigger DDL
Important: For trigger WHEN clauses, always use pg_get_expr(t.tgqual, t.tgrelid, false) from pg_catalog.pg_trigger. Do NOT use information_schema.triggers.action_condition.
Workflow
- Identify the object type you're implementing
- Find the pg_dump function from the table above
- Read the system catalog query — note which columns, joins, and helper functions are used
- Check version-specific handling — pg_dump uses
fout->remoteVersionchecks - Adapt for pgschema in
ir/inspector.goorir/queries/:- Use pgx parameter binding
- Handle NULLs appropriately
- Add version detection if needed
When pg_dump is Authoritative
Always reference for: system catalog query patterns, correct use of pg_get_* functions, version-specific feature detection, object dependency tracking.
When NOT to Copy pg_dump
Don't copy: output formatting (pgschema has different conventions), archive/restore logic, full-database scope (pgschema is schema-focused), pre-PG14 compatibility.
pgschema Adaptation Pattern
// pg_dump query pattern:
// SELECT t.tgname, pg_get_expr(t.tgqual, t.tgrelid, false) as when_clause
// FROM pg_catalog.pg_trigger t WHERE ...
// pgschema adaptation (in ir/inspector.go or ir/queries/):
query := `SELECT t.tgname, pg_get_expr(t.tgqual, t.tgrelid, false)
FROM pg_catalog.pg_trigger t
WHERE t.tgrelid = $1 AND NOT t.tgisinternal`
rows, err := conn.Query(ctx, query, tableOID)Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

