Back to Graph Theory Series

Part 18: Special Graph Families, Isomorphism & Minors

September 6, 2026 Wasil Zafar 32 min read

A 20-paper, two-decade proof effort by two mathematicians showed that an astonishing range of graph properties — planarity among them — all reduce to checking a finite list of forbidden patterns.

Table of Contents

  1. A Bit of History
  2. Special Graph Families
  3. Perfect Graphs
  4. The Graph Isomorphism Problem
  5. Graph Minors
  6. The Robertson-Seymour Theorem
  7. Treewidth & Tree Decompositions
  8. Real-World Applications
  9. Exercises
  10. Conclusion & Next Steps

A Bit of History

This part gathers three separate but deeply connected threads:

  • Claude Berge (whose augmenting-path matching theorem appeared in Part 16) conjectured in 1961 what became known as the Strong Perfect Graph Conjecture — a deep structural statement about "perfect" graphs. It stood open for 45 years until Maria Chudnovsky, Neil Robertson, Paul Seymour, and Robin Thomas finally proved it in 2006, in a paper spanning well over 150 pages.
  • The graph isomorphism problem — deciding whether two graphs are structurally identical — sat for decades in a strange complexity limbo: known to be in NP, but neither known to be solvable in polynomial time nor proven NP-complete. In 2015, László Babai announced a quasipolynomial-time algorithm, a landmark result that made global headlines in the theoretical computer science community (and was itself briefly retracted and then re-confirmed after a gap was found and fixed in 2017 — a vivid reminder that even celebrated proofs get scrutinized and strengthened).
  • Neil Robertson and Paul Seymour spent from 1983 to 2004 publishing a sequence of over 20 papers, collectively titled "Graph Minors," culminating in a proof of what was previously Wagner's conjecture: every graph property closed under taking minors can be characterized by a finite list of forbidden minors. It is widely regarded as one of the deepest and most difficult results in all of combinatorics, and it earned both mathematicians the prestigious Fulkerson Prize.

Special Graph Families

Beyond the families introduced in Part 4 (trees, bipartite, complete graphs), several structured families recur throughout advanced graph theory. The important idea is not just that these families have names: each family forbids or organizes certain patterns, and that extra structure often turns a problem that is difficult on arbitrary graphs into one that can be solved efficiently.

Structure at a Glance Special Families

Three ways a graph can carry extra structure

Think of a graph family as a promise about the input. A good promise removes pathological cases and exposes an ordering, geometry, or recursive decomposition that an algorithm can exploit.

Three structured graph families A chordal graph with a diagonal chord, an interval representation and its overlap graph, and a recursively composed cograph. Structure is algorithmic leverage Chordal graph long cycles get shortcuts chord Perfect elimination orderings appear. Interval graph geometry explains adjacency ABC Overlap becomes an edge. Cograph built recursively JOIN UNION Decompose, solve pieces, recombine.
  • Chordal graphs: every cycle of length 4 or more has a chord — an edge connecting two non-adjacent vertices of that cycle. This destroys the long induced cycles that make many problems difficult.
  • Interval graphs: vertices represent intervals on a real line, with edges between overlapping intervals. The geometry itself gives an ordering and makes them a natural model for scheduling and resource allocation.
  • Cographs (complement-reducible graphs): built recursively from single vertices using disjoint union and join/complement operations. Their recursive construction gives a decomposition tree on which many problems can be solved bottom-up.

Perfect Elimination: Why Chordal Graphs Are Friendly

A vertex is simplicial when all of its neighbors form a clique. A perfect elimination ordering (PEO) repeatedly removes a simplicial vertex until nothing remains. Chordal graphs are exactly the graphs that admit such an ordering. Algorithmically, this means we can peel the graph apart without creating a complicated boundary: when a vertex is eliminated, all of the still-relevant neighbors already know about one another.

Perfect Graphs

Recall from Part 13 that every clique of size \(k\) forces at least \(k\) colors, so \(\omega(G) \le \chi(G)\) always. A graph is perfect when this obvious lower bound is never loose — not just for the graph itself, but for every induced subgraph.

$$G\text{ is perfect}\quad\Longleftrightarrow\quad \chi(H)=\omega(H)\text{ for every induced subgraph }H\subseteq G.$$
Perfect vs. Imperfect

The gap \(\chi-\omega\) is the obstruction

The 5-cycle is the smallest clean example of imperfection: its largest clique has only two vertices, but an odd cycle still requires three colors.

Perfect and imperfect coloring examples A chordal four-vertex graph has clique number and chromatic number three, while the five-cycle has clique number two and chromatic number three. When does the clique lower bound exactly predict coloring? Perfect example ω = 3, χ = 3 Imperfect witness: C₅ ω = 2, χ = 3

Bipartite graphs and chordal graphs are perfect. Odd cycles of length at least 5, called odd holes, are not; neither are their complements, called odd antiholes. Berge's Strong Perfect Graph Theorem (conjectured in 1961 and proved decades later) says these are exactly the obstructions: a graph is perfect if and only if it contains no odd hole and no odd antihole as an induced subgraph.

Why “Every Induced Subgraph” Matters

A graph might accidentally satisfy \(\chi(G)=\omega(G)\) while hiding a smaller induced subgraph where the equality fails. Perfectness is hereditary: every time you zoom in by deleting vertices, the equality must survive.

The Graph Isomorphism Problem

Two graphs \(G_1\) and \(G_2\) are isomorphic when one can be relabeled to become the other. Geometry does not matter: vertices may move, edges may bend, and labels may change. What must remain unchanged is which pairs are adjacent.

$$G_1\cong G_2\quad\Longleftrightarrow\quad \exists\text{ bijection }\phi:V(G_1)\to V(G_2)\text{ such that }uv\in E(G_1)\iff \phi(u)\phi(v)\in E(G_2).$$
Same Structure, Different Labels

Do not compare drawings — compare adjacency

Two isomorphic graphs under a vertex relabeling Two differently drawn five-vertex graphs have the same adjacency under the mapping A to 3, B to 5, C to 1, D to 4, and E to 2. Isomorphism asks whether a relabeling makes the edge sets identical Graph G₁ ABCDE Graph G₂ 35142 One valid mapping A maps to 3B maps to 5C maps to 1D maps to 4; E maps to 2

Invariants Are Filters, Not Usually Proofs

Isomorphic graphs must have the same number of vertices and edges, the same degree multiset, the same number of connected components, the same cycle counts, and many other graph invariants. A mismatch instantly proves two graphs are not isomorphic. But matching invariants usually does not prove they are isomorphic: different graphs can share many summaries. A true isomorphism needs a globally consistent vertex correspondence.

Determining isomorphism in general is famously unusual in complexity theory: it is in NP, not known to be NP-complete, and no general polynomial-time algorithm is known. Babai's quasipolynomial-time breakthrough dramatically narrowed the gap, while the search for a polynomial-time algorithm remains open.

Graph Minors

Isomorphism asks whether we can change labels while preserving the graph exactly. Minor theory moves in the opposite direction: it deliberately forgets detail while trying to preserve coarse connectivity structure. A graph \(H\) is a minor of \(G\) if \(H\) can be obtained through vertex deletion, edge deletion, and edge contraction.

Delete vs. Contract: Three Ways to Simplify

The three graph minor operations Starting from a small graph, separate panels show deleting an edge, deleting a vertex, and contracting an edge. A minor keeps the coarse connectivity and throws away detail Start Delete an edge remove one relationship Delete a vertex remove a vertex + incident edges Contract an edge u+v merge two endpoints
RelationAllowed operationWhat it preserves
SubgraphDelete vertices/edgesExact surviving adjacencies
Induced subgraphDelete vertices onlyAll edges among surviving vertices
MinorDelete + contractCoarse connectivity pattern

A graph family is minor-closed if simplifying any member by these operations never leaves the family. Planar graphs are the model example: deleting or contracting inside a planar embedding cannot force crossings. Wagner's theorem therefore recognizes planarity by the two minors that must never appear, \(K_5\) and \(K_{3,3}\).

Isomorphism vs. Minor: Exactness vs. Simplification

Isomorphism: “Are these exactly the same structure after relabeling?”   Minor: “Can this simpler structure be extracted by deleting and contracting?” The first preserves everything; the second intentionally forgets detail.

The Robertson-Seymour Theorem

The crown jewel of minor theory is easiest to appreciate as a statement about obstructions. Suppose a property survives every deletion and contraction. Then failure of that property must have some minimal causes — graphs that fail the property, but whose proper minors no longer do. Robertson and Seymour proved that there can only be finitely many such minimal forbidden patterns.

Forbidden-Pattern View

Infinite family, finite obstruction list

Planarity is the perfect miniature example: there are infinitely many planar graphs and infinitely many non-planar graphs, but the entire boundary between them is controlled by just two forbidden minors.

Finite forbidden-minor characterization intuition An arbitrary graph is simplified and tested for a finite obstruction set; planarity uses K5 and K3,3 as the obstructions. Minor-closed property = “avoid a finite set of bad cores” Input graph G delete / contract Finite obstruction set K₅bad core K₃,₃bad core For planarity, the list has size 2. Decision contains one: reject contains none: accept

The theorem is existential in a striking way: it guarantees that a finite obstruction list exists for every minor-closed family, but the theorem alone does not hand us that list for a property we care about. Finding explicit obstruction sets can itself be extremely difficult. The conceptual payoff is still enormous: a potentially infinite universe of counterexamples is controlled by finitely many minimal patterns.

Treewidth & Tree Decompositions

Treewidth measures how far a graph is from behaving like a tree. The key trick is not to force the original graph itself into a tree. Instead, we build a tree of overlapping bags, where each bag stores a small local interface of vertices. If those interfaces stay small, dynamic programming can solve a global problem by passing compact summaries from bag to bag.

The Three Rules for a Valid Tree Decomposition

1. Cover vertices
Every graph vertex appears in at least one bag.
2. Cover edges
For every edge \(uv\), some bag contains both \(u\) and \(v\).
3. Running intersection
All bags containing a fixed vertex form one connected subtree.
$$\operatorname{width}(T)=\max_{B\in T}(|B|-1),\qquad \operatorname{tw}(G)=\min_T \operatorname{width}(T).$$
Treewidth Intuition

A cycle is not a tree, but it can be processed through bags of size 3

For \(C_5\), the bags below each contain three vertices, so this decomposition has width \(3-1=2\). The repeated vertex 1 acts like a small interface that keeps the local pieces consistent.

Tree decomposition of a five-cycle The five-cycle is shown beside a three-bag path with bags 1,2,3; 1,3,4; and 1,4,5, demonstrating width two. Tree decomposition = overlapping local windows Original graph C₅ 12345 One width-2 decomposition Bag 1{1, 2, 3} Bag 2{1, 3, 4} Bag 3{1, 4, 5} Largest bag has 3 vertices; width = 2

Trees have treewidth 1, cycles have treewidth 2, and complete graphs \(K_n\) have treewidth \(n-1\). High treewidth means every decomposition needs a large interface somewhere; low treewidth means the graph can be separated into pieces that interact through only a few shared vertices.

Why This Makes Hard Problems Easier

A dynamic program does not need to remember the entire processed graph. It only remembers enough information about the current bag to connect the solved part to the unsolved part. For many classic problems, this leads to runtimes of the form \(f(k)\,n\) or \(f(k)\,n^{O(1)}\), where \(k\) is treewidth. The dependence on \(k\) may be exponential, but when \(k\) is small the algorithm can still be practical on large graphs.

Real-World Applications

Case Study DatabasesQuery Optimization

Database Query Optimization via Treewidth

Complex join queries can be modeled by a graph or hypergraph whose vertices are relations/variables and whose edges encode interactions. When this structure has low treewidth, the query can often be decomposed into small overlapping pieces and evaluated by dynamic programming. High width means some intermediate interface is inherently large, which is exactly where intermediate join results can explode.

Join graph and tree decomposition intuition A cyclic join graph is decomposed into three overlapping bags, illustrating how a query engine can solve local joins and combine summaries. Treewidth turns one tangled join into small overlapping local joins Join interaction graph ABCDE Process overlapping bags {A,B,C}{A,C,D}{A,D,E} Small interfaces keep intermediate state manageable.

Part 18 Mental Model

Special families
Extra structure creates useful orderings/decompositions.
Perfect graphs
Clique lower bound exactly matches coloring in every induced subgraph.
Isomorphism
Preserve the graph exactly; only labels/drawing change.
Minors
Simplify by deletion/contraction to expose hidden cores.
Robertson–Seymour
Minor-closed families have finitely many forbidden cores.
Treewidth
Small overlapping interfaces make global DP possible.

Exercises

  1. Verify that any tree is a chordal graph, and explain why (hint: trees have no cycles of length 4 or more to begin with, so the chordal condition holds vacuously).
  2. Explain the difference between a graph subdivision (used in Kuratowski's theorem) and a graph minor (used in Wagner's theorem), giving a small example where a graph is a minor of another but not a subdivision.
  3. Compute the treewidth of a simple cycle graph \(C_5\) by constructing an explicit tree decomposition and identifying its largest bag.
  4. Challenge: Research one specific minor-closed graph family beyond planar graphs (e.g., graphs embeddable on the torus, or graphs of bounded treewidth) and identify (or look up) its forbidden-minor characterization.

Conclusion & Next Steps

From perfect graphs to isomorphism to the sweeping Robertson-Seymour theorem, this part has shown just how much structure hides beneath "does this graph look like that one." The next part turns from structural characterization to counting: how many edges can a graph have before it is forced to contain a particular substructure — the domain of extremal and Ramsey theory.

Next in the Series

In Part 19: Extremal Graph Theory & Ramsey Theory, we'll meet Ramsey's theorem, Turán's theorem, and the surprising guarantee that complete disorder is impossible once a structure grows large enough.