Case 31 — Goliath and Elhanan

Audience

Skeptics who treat this as one of the cleanest, most embarrassing numerical/narrative contradictions in the Old Testament — two different men credited with killing the same famous giant, in two different books, with a third text appearing to try to fix the problem by inventing a brother for Goliath to kill instead.

The Tension

1 Samuel 17 narrates, at length and in famous detail, David's killing of Goliath the Gittite with a sling and stone. 2 Samuel 21:19, in a much shorter list of exploits against Philistine giants during David's later reign, states: "Elhanan son of Jair the Bethlehemite killed Goliath the Gittite, the shaft of whose spear was like a weaver's rod." Same giant, same distinctive weapon description (the weaver's-rod spear also appears in 1 Samuel 17:7), different killer, different weapon. 1 Chronicles 20:5, covering the same list of exploits, reads: "Elhanan son of Jair killed Lahmi the brother of Goliath the Gittite, the shaft of whose spear was like a weaver's rod" — apparently resolving the problem by giving Goliath a brother for Elhanan to have killed instead.

The Load-Bearing Assumption

That the Masoretic Hebrew text of 2 Samuel 21:19, as it has come down through the manuscript tradition, perfectly preserves what the original author wrote, with no possibility of scribal corruption at exactly the point where the difficulty lies. This is the same governing principle already established for the census numbers (Case 1/7) and the Age of Ahaziah (Case 1/9), and it applies here with unusual clarity because the correction is preserved within Scripture's own textual witness rather than requiring appeal to evidence outside it.

The Textual Mechanism

The Hebrew text of 2 Samuel 21:19, examined closely, shows signs of a specific, identifiable corruption: the word for "Bethlehemite" (bêt hallaḥmî) sits immediately before "Goliath," and the object marker/word for "brother of" ('et-ḥî) is a short sequence of letters easily lost through haplography — a scribe's eye skipping a repeated or similar letter sequence during copying, a well-documented category of transmission error distinct from, but structurally identical in kind to, the kaf/mem confusion already documented for Ahaziah's age in Case 1/9. 1 Chronicles 20:5, drawing on either a better-preserved exemplar or the same source before the corruption entered the 2 Samuel textual line, retains "the brother of" ('et-laḥmî 'aḥî golyāt) intact. The Septuagint and other ancient versions show additional evidence of scribes wrestling with exactly this verse, further indicating the difficulty was recognized and worked with in antiquity rather than invented by modern criticism.

Why the Corrected Reading Is Not Special Pleading

Unlike a harmonization invented solely to rescue an embarrassing text, this correction rests on: (1) an identifiable, well-attested category of scribal error (haplography around near-identical letter sequences); (2) an independent parallel passage (1 Chronicles 20:5) that preserves what appears to be the uncorrupted reading; (3) the same weaver's-rod-spear detail appearing in both the Goliath account and the Elhanan account, suggesting the author of 2 Samuel 21 always intended a connection between the two giants, brothers with matching distinctive weaponry, not a rival, competing tradition about who actually killed the famous giant. Most modern critical translations (NIV, NET, ESV footnotes) reflect this in their handling or footnoting of 2 Samuel 21:19.

The Alternative, Held Honestly

A minority position holds that 1 Samuel 17's Goliath account was itself later composed or embellished, attaching an existing giant-slaying tradition (Elhanan's) to David for royal-legitimation purposes, with 1 Chronicles 20:5 representing an even later harmonizing correction rather than a preservation of the original reading. This position is held by some critical scholars and deserves to be named rather than dismissed; it does not, however, have stronger textual-critical grounding than the scribal-corruption reading, which has both an identifiable mechanism and independent textual attestation in its favor.

The Connection to What Matters

Whichever giant Elhanan faced, the text preserves an important detail this case should not let pass unnoticed: David was not the only man in Israel's history who stood against an armed giant and won. He was the most famous, and the story of his fight rightly dominates the tradition — a shepherd boy, five stones, and a God who does not need the size of the weapon to match the size of the threat. But Elhanan, killing Goliath's own brother with the same family's terrifying spear, in a later, less celebrated skirmish, is a reminder that the God who gave David his victory kept giving that same kind of victory to men whose names barely survive a single verse of genealogical listing. The Kingdom does not run on famous victories alone. It runs on a God who is equally present, equally sufficient, in the battle nobody remembers as in the one that becomes Scripture's most beloved story.

Precedent Note

Tyndale House's 2022 article and Kaspars Ozoliņš at Text & Canon both lay out the haplography argument with the relevant Hebrew detail. The minority critical position (embellishment/later harmonization) is represented at Wikipedia's Elhanan entry and should be named rather than dismissed, though the textual evidence favors the scribal-corruption reading.

Cross-References

Depends on: Case 1/7. Case 1/9. | Resolution: External challenge substantially resolved by identified scribal corruption, confirmed by an independent parallel text; among the more complete resolutions in this category.