agentleFS
pgplexpgplex/pgschema/.claude/skills/pg_dump/SKILL.md

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

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 0 mentionsMar 2026: 2 mentionsApr 2026: 2 mentionsMay 2026: 0 mentionsJun 2026: 1 mentionJul 2026: 0 mentionsAug 2026: 2 mentionsSep 2026: 3 mentionsOct 2026: 8 mentionsNov 2026: 4 mentions
Dec 2025Jun 2026Nov 2026
Mentions a month of the pgplex/pgschema repository that our weekly crawl found. There is no adoption data for this file yet.

Most recently taken up by

Who's talking about pgplex/pgschema

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

17 more on GitHub
  • Other versions1 project uses a version of this.

    Word for word · 1

    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.

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
  1. Distinctive:

    Use pgx parameter binding

    line 52
  2. Distinctive:

    Add version detection if needed

    line 54
  3. Very specific:

    Always reference for: system catalog query patterns, correct use of pg_get_* functions, version-specific feature detection, object …

    line 58
  4. Very specific:

    Don't copy: output formatting (pgschema has different conventions), archive/restore logic, full-database scope (pgschema is …

    line 62

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 queries
  • pg_dump.h - Data structures
  • pg_dump_sort.c - Dependency sorting
  • common.c - Shared catalog query utilities

Object Type → pg_dump Function → System Catalogs

ObjectFunctionCatalogs
Tables & ColumnsgetTables()pg_class, pg_attribute, pg_type
ConstraintsgetConstraints()pg_constraint
IndexesgetIndexes()pg_index, pg_class
TriggersgetTriggers()pg_trigger, pg_proc
FunctionsgetFuncs()pg_proc
ViewsgetViews()pg_class, pg_rewrite
SequencesgetSequences()pg_sequence, pg_class
PoliciesgetPolicies()pg_policy
TypesgetTypes()pg_type
AggregatesgetAggregates()pg_aggregate, pg_proc
CommentsgetComments()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 DDL
  • pg_get_indexdef(oid, column, pretty) - Get index DDL
  • pg_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

  1. Identify the object type you're implementing
  2. Find the pg_dump function from the table above
  3. Read the system catalog query — note which columns, joins, and helper functions are used
  4. Check version-specific handling — pg_dump uses fout->remoteVersion checks
  5. Adapt for pgschema in ir/inspector.go or ir/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)

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.