# If I have read-only tables in Postgres, should I index them heavily?

DevFeed: [If I have read-only tables in Postgres, should I index them heavily?](<https://devfeed.tech/articles/if-i-have-read-only-tables-in-postgres-should-i-index-them-heavily-5434.md>)

Original publisher: [Read original article](<https://neon.com/blog/if-i-have-read-only-tables-in-postgres-should-i-index-them-heavily>)

Author: Rishi Raj Jain

Published: 2024-07-17T14:06:50Z

Content type: tutorial

Language: en

Sources: [Blog -- Neon Docs](<https://devfeed.tech/sources/blog-neon-docs.md>)

Topics: [data](<https://devfeed.tech/topics/data.md>)

Tags: [complexity](<https://devfeed.tech/tags/complexity.md>), [database](<https://devfeed.tech/tags/database.md>), [optimization](<https://devfeed.tech/tags/optimization.md>), [performance](<https://devfeed.tech/tags/performance.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [search](<https://devfeed.tech/tags/search.md>), [sorting](<https://devfeed.tech/tags/sorting.md>)

## AI overview

The article explains how to choose indexing strategies for small read-only or read-heavy Postgres tables. It emphasizes that query complexity, including range queries, multi-column filters, and sorting, should guide the choice between light and heavy indexing.

## Source excerpt

We often get questions about Postgres indexing strategies, and read-only (or read-heavy) tables are especially interesting. This post was actually inspired by this question on Reddit: "I have a table with about 20 columns that each have Boolean values indicating whether the row h...