Skip to main content

Indexing PostgreSQL with Apache Solr

Image
By
This article explains how to offload heavy IP search and filtering workloads from PostgreSQL to Apache Solr to gain speed, scalability and richer query capabilities. PostgreSQL remains the system of record for IP ranges and geolocation data, while Solr—backed by Lucene’s inverted indexes—handles fast range lookups and flexible text queries over fields like country, state and city. The piece walks through creating a Solr core, defining an IP-focused schema, wiring PostgreSQL to Solr via the DataImportHandler, and running full imports so Solr can be queried for IP ranges and geo filters with simple syntax. The takeaway: combining Postgres for storage and Solr for search yields a robust, scalable IP management stack that outperforms pure SQL approaches for complex, high-volume search use cases.

Searching and filtering large IP address datasets within PostgreSQL can be challenging. Why? Databases excel at data storage and structured queries, but often struggle with full-text search and complex analysis. Apache Solr, a high-performance search engine built on top of Lucene, is designed to handle these tasks with remarkable speed and flexibility.

What do we need?

  • A running PostgreSQL database with a table containing IP address information (named "ip_loc" in our example).
  • A basic installation of Apache Solr.

Setting up Apache Solr

1. Create a Solr Core:

solr create -c ip_data -d /path/to/solr/configsets/

2. Define the Schema (schema.xml)

<field name="start_ip" type="ip" indexed="true" stored="true"/>
<field name="end_ip" type="ip" indexed="true" stored="true"/>
<field name="iso2" type="string" indexed="true" stored="true"/>
<field name="state" type="text_general" indexed="true" stored="true"/>
<field name="city" type="text_general" indexed="true" stored="true"/>

Integrating PostgreSQL and Solr

Solr's DataImportHandler (DIH): Add the following DIH configuration to your solrconfig.xml:

<dataConfig>
    <dataSource type="JdbcDataSource" 
                driver="org.postgresql.Driver"
                url="jdbc:postgresql://localhost/your_database"
                user="your_username" 
                password="your_password"/>
    <document>
        <entity name="ip_data" query="SELECT * FROM ip_loc">
            <field column="start_ip" name="start_ip" /> 
            </entity>
    </document>
</dataConfig>

Import Data: Initiate the data import using the Solr admin interface or the command line:

http://localhost:8983/solr/ip_data/dataimport?command=full-import

Querying Solr

  • IP Range Search: start_ip:[192.168.0.1 TO 192.168.255.255]
  • Geolocation Filtering: iso2:US AND state:California
  • Combined Search: city:NewYork AND start_ip:[10.0.0.0 TO 10.255.255.255]

Benefits vs. Pure PostgreSQL

  1. Performance: Solr's inverted indexes provide superior search speed.
  2. Scalability: Solr easily distributes across multiple machines.
  3. Flexibility: Solr's query syntax offers rich search capabilities.

My take

By combining PostgreSQL and Apache Solr, you create a robust IP address management system that scales efficiently while providing lightning-fast search functionality.

Related guides:

If you need help with distributed systems, backend engineering, or data platforms, check my Services.

Labels:

Most read articles

Why Is Customer Obsession Disappearing?

By
Many companies trade real customer-obsession for automated, low-empathy support. Through examples from Coinbase, PayPal, GO Telecommunications and AT&T, this article shows how reliance on AI chatbots, outsourced call centers, and KPI-driven workflows erodes trust, NPS and customer retention. It argues that human-centric support—treating support as strategic investment instead of cost—is still a core growth engine in competitive markets. It's wild that even with all the cool tech we've got these days, like AI solving complex equations and doing business across time zones in a flash, so many companies are still struggling with the basics: taking care of their customers. The drama around Coinbase's customer support is a prime example of even tech giants messing up. And it's not just Coinbase — it's a big-picture issue for the whole industry. At some point, the idea of "customer obsession" got replaced with "customer automation," and no...
Read more

What the Heck is Superposition and Entanglement?

By
This post is about superposition and interference in simple, intuitive terms. It describes how quantum states combine, how probability amplitudes add, and why interference patterns appear in systems such as electrons, photons and waves. The goal is to give a clear, non mathematical understanding of how quantum behavior emerges from the rules of wave functions and measurement. If you’ve ever heard the words superposition or entanglement thrown around in conversations about quantum physics, you may have nodded politely while your brain quietly filed them away in the "too confusing to deal with" folder.  These aren't just theoretical quirks; they're the foundation of mind-bending tech like Google's latest quantum chip, the Willow with its 105 qubits. Superposition challenges our understanding of reality, suggesting that particles don't have definite states until observed. This principle is crucial in quantum technologies, enabling phenomena like quantum comp...
Read more

SynthLink Compared to Google’s Natural Questions: A Practical Evaluation

By
SynthLink evaluates reasoning, synthesis and internal consistency across diverse question types. Google’s Natural Questions evaluates extractive QA: finding short text spans inside structured documents. Because real workloads require interpretation, abstraction and multi-step logic, SynthLink exposes capabilities and failure modes that NQ cannot measure. The two benchmarks are complementary, but SynthLink is more aligned with production tasks. Benchmarks such as Google’s Natural Questions (NQ) dominate model evaluation. They provide a reliable, academically stable test for extractive question answering: short queries, grounded answers, and constrained context ranges. But real workloads rarely look like NQ. Production systems must handle ambiguous inputs, multi-step reasoning, poorly structured prompts, and cases where no canonical answer exists. SynthLink was designed for this broader landscape. It focuses on evaluating reasoning, synthesis and internal consistency rather than snippe...
Read more