fix: add domain.name indexes to subgraph schema

[shrugs]

references #1819

Summary

• re-enables the domain.name index (disabled in Create byName index on subgraph_domains table #1819) using a hash index to avoid the btree 8191-byte row size limit caused by spam names
• hash index supports exact name lookups without size constraints

Out of Scope

• GIN trigram index (gin_trgm_ops) for partial match operations (_contains, _starts_with, _ends_with)
  • requires pg_trgm extension, which is obviously available, but not sure how best to ensure that the CREATE EXTENSION IF NOT EXISTS pg_trgm command is executed before ponder applies indexes. maybe could be part of ensdbwriterworker?

[changeset-bot]

⚠️ No Changeset found

Latest commit: be4e92e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

3 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
admin.ensnode.io	Skipped		Mar 31, 2026 8:41pm
ensnode.io	Skipped		Mar 31, 2026 8:41pm
ensrainbow.io	Skipped		Mar 31, 2026 8:41pm

[coderabbitai]

📝 Walkthrough

Walkthrough

Updated the subgraph_domain table's index configuration by removing a previously disabled byName index and adding a new byExactName hash index on the name column. Other existing indexes on labelhash, parentId, ownerId, registrantId, wrappedOwnerId, and resolvedAddressId remain unchanged.

Changes

Cohort / File(s)	Summary
Index Configuration Update packages/ensdb-sdk/src/ensindexer-abstract/subgraph.schema.ts	Replaced disabled byName index with new byExactName hash index on t.name in the subgraph_domain table.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related issues

• Create byName index on subgraph_domains table #1819: Modifies the same subgraph_domain table name column indexing; the byExactName hash index likely addresses the index size/error issue described in this ticket.

Possibly related PRs

• add missing index on domain name column #1747: Adds a byName index on t.name for the subgraph_domain table, which this PR replaces with a hash-based approach.
• Disable byName index on subgraph_domains table #1820: Disables the byName index on the same column; this PR continues that work by removing it entirely and introducing the byExactName hash index.

Poem

🐰 An index grew too large, you see,
So hash we hash instead of B-tree!
Exact names indexed with care,
Swift queries dance through data fair! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description provides a clear summary of changes, references a related issue, and explains the rationale. However, the Testing and Pre-Review Checklist sections required by the template are completely missing.	Add the 'Testing' section explaining how this change was tested, and complete the 'Pre-Review Checklist' with checkmarks for both blocking items or explanations if not applicable.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: adding domain.name indexes to the subgraph schema, which matches the core modification in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/name-index

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

Re-enables an index on subgraph_domains.name in the ENS subgraph-compatible Ponder/Drizzle schema, switching from a btree index to a hash index to avoid Postgres’ btree index-row size limit when spam/oversized names are present.

Changes:

• Add a hash index on subgraph_domains.name (byExactName) to support exact-match lookups without hitting the btree 8191-byte limit.
• Remove the prior commented-out/disabled byName index block.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[vercel]

Suggested change

	byExactName: index().using("hash", t.name),
	byExactName: index().using("hash").on(t.name),

Incorrect hash index syntax: index().using("hash", t.name) passes column as second parameter instead of using .on() method

[tk-o]

The update looks good to me 👍 As discussed on Slack, it'd great to enable the pg_trgm extension for ENSDb within the prepareIndexingSetup function that will be added in PR #1843.