@_avichawla: How Cloudflare cut query times by 35x without leaving Postgres: Their Postgres tables hit billions of rows, and every t…

X AI KOLs Timeline News

Summary

Cloudflare improved query performance by 35x on billion-row Postgres tables using TimescaleDB (Tiger Cloud), and built a real-time earthquake dashboard with Claude Code and Tiger CLI.

How Cloudflare cut query times by 35x without leaving Postgres: Their Postgres tables hit billions of rows, and every time-range query started getting slower. Plain Postgres scans the entire table on every query, regardless of the time window. They tried the manual route by building precomputed aggregates with cron jobs and evaluating ClickHouse, which needed a full ingestion pipeline just to handle their write pattern. Here's where most teams get stuck at exactly this point. They utilize manual partitioning, splitting data into child tables by day or month. Then they wire up cron jobs to refresh aggregate tables. Every schema change after that requires updating the cron logic and coordinating across teams. The infrastructure becomes the project. Tiger Cloud is managed TimescaleDB by @TigerDatabase on the Postgres you already know, with automatic time-based partitioning, continuous aggregates, and compression built in from the start. Cloudflare moved to TimescaleDB after exhausting the manual route and saw 5-35x query performance improvement on the same data. Here is how it works: → Hypertables partition data by timestamp automatically. Every time-range query hits only the relevant chunk, not the full table. → Continuous aggregates refresh incrementally in the background, with no cron jobs to maintain. To show what this looks like in practice, I built a real-time earthquake intelligence dashboard on a 3D globe using Claude Code and Tiger Cloud in a single session. The USGS earthquake catalog has 400,000+ events since 1900, each a timestamped row. The dashboard plots them as ripple animations sized by magnitude and colored by depth, with a time slider that scrubs through 120 years of seismic history. Every slider position fires a live query against the hypertable, and the side panel pulls from continuous aggregates. Claude Code connected to Tiger Cloud through the Tiger CLI MCP server, provisioned the database, pulled the USGS catalog, and assembled the full Next.js and Three.js frontend without leaving the session. The video below shows the final build in action, and I worked with the Tiger Data team to put this together. Tiger CLI is open-source (Apache 2.0) and works with Claude Code, Cursor, Codex, Gemini CLI, and VS Code. To try this yourself: → Sign up for Tiger Cloud here: https://fandf.co/4w3FIbA. New accounts get $1,000 in free credits, no credit card required. → Install Tiger CLI: curl -fsSL https(:)//cli(.)tigerdata(.)com | sh → Run tiger mcp install claude-code → Give Claude Code a prompt and let it build. I also wrote a full walkthrough on how you can turn any coding agent into a production-grade data engineer that can manage over a billion-row Postgres workloads. It covers everything from the database setup to the final build. Read it below.
Original Article
View Cached Full Text

Cached at: 08/17/26, 10:34 AM

How Cloudflare cut query times by 35x without leaving Postgres:

Their Postgres tables hit billions of rows, and every time-range query started getting slower.

Plain Postgres scans the entire table on every query, regardless of the time window.

They tried the manual route by building precomputed aggregates with cron jobs and evaluating ClickHouse, which needed a full ingestion pipeline just to handle their write pattern.

Here’s where most teams get stuck at exactly this point.

They utilize manual partitioning, splitting data into child tables by day or month. Then they wire up cron jobs to refresh aggregate tables.

Every schema change after that requires updating the cron logic and coordinating across teams. The infrastructure becomes the project.

Tiger Cloud is managed TimescaleDB by @TigerDatabase on the Postgres you already know, with automatic time-based partitioning, continuous aggregates, and compression built in from the start.

Cloudflare moved to TimescaleDB after exhausting the manual route and saw 5-35x query performance improvement on the same data.

Here is how it works:

→ Hypertables partition data by timestamp automatically. Every time-range query hits only the relevant chunk, not the full table.

→ Continuous aggregates refresh incrementally in the background, with no cron jobs to maintain.

To show what this looks like in practice, I built a real-time earthquake intelligence dashboard on a 3D globe using Claude Code and Tiger Cloud in a single session.

The USGS earthquake catalog has 400,000+ events since 1900, each a timestamped row. The dashboard plots them as ripple animations sized by magnitude and colored by depth, with a time slider that scrubs through 120 years of seismic history.

Every slider position fires a live query against the hypertable, and the side panel pulls from continuous aggregates.

Claude Code connected to Tiger Cloud through the Tiger CLI MCP server, provisioned the database, pulled the USGS catalog, and assembled the full Next.js and Three.js frontend without leaving the session.

The video below shows the final build in action, and I worked with the Tiger Data team to put this together.

Tiger CLI is open-source (Apache 2.0) and works with Claude Code, Cursor, Codex, Gemini CLI, and VS Code.

To try this yourself:

→ Sign up for Tiger Cloud here: https://fandf.co/4w3FIbA.

New accounts get $1,000 in free credits, no credit card required.

→ Install Tiger CLI: curl -fsSL https(:)//cli(.)tigerdata(.)com | sh

→ Run tiger mcp install claude-code

→ Give Claude Code a prompt and let it build.

I also wrote a full walkthrough on how you can turn any coding agent into a production-grade data engineer that can manage over a billion-row Postgres workloads.

It covers everything from the database setup to the final build.

Read it below.


Postgres for time-series workloads at any scale | Tiger Data

Source: https://www.tigerdata.com/go/kol?utm_source=x&utm_medium=affiliate&utm_campaign=fnf-july&utm_content=achawla-1kcredits-tsdb TigerData logo

TigerData logo

Get started

Real-world scale of a single Tiger Cloud service.

// What’s included

Core capabilities

// pg_textsearch + pgvectorscale

Two Extensions. Complete Search.

BM25 keyword search and vector similarity search, both running natively in Postgres. No separate search infrastructure, no ETL, no sync lag.

CREATE INDEX ON documents USING bm25\(content\) WITH \(text\_config='english'\); SELECT \* FROM documents ORDER BY content <@\> 'database system' LIMIT 10;

Modern ranked text search as a native Postgres extension. Industry-standard BM25 scoring with the <@> operator, Block-Max WAND optimization, and parallel index builds.

Works with your tools

Drop it into Claude Code, Cursor, Codex, Gemini CLI, or VS Code. No context switching, no new workflow to learn.

tiger data logo

Plug into your stack

Use Tiger Data with your preferred cloud provider, and the wider Postgres ecosystem.

Explore integrations

// enterprise

Enterprise ready by default

Enterprise Trust

Contractual uptime SLAs, regional data isolation and enterprise-ready compliance certifications.

24/7 Support

Round-the-clock coverage with global Postgres experts and guaranteed enterprise response times.

Similar Articles

Scaling PostgreSQL to power 800 million ChatGPT users

OpenAI Blog

OpenAI shares technical insights on scaling PostgreSQL to support 800 million ChatGPT users and millions of queries per second, using a single-primary architecture with 50 read replicas while managing challenges from write-heavy workloads through sharding and optimization strategies.

How TimescaleDB compresses time-series data

Hacker News Top

This article explains how TimescaleDB's hypercore engine achieves up to 98% compression for time-series data using columnar storage and specialized algorithms like delta encoding and Gorilla XOR, and contrasts it with PostgreSQL's TOAST.

ParadeDB Search Performance Improvements

Hacker News Top

ParadeDB responds to PlanetScale's new TIN Postgres text-search extension by closing its 8x BM25 performance gap through optimization passes rather than architectural changes, benchmarking both on the same StackExchange dataset.

@posthog: https://x.com/posthog/status/2062595534381326421

X AI KOLs Timeline

PostHog used an AI agent based on Karpathy's autoresearch to find a three-year-old bug in their ClickHouse query engine that prevented proper primary key usage for timestamp filters. Fixing it improved performance by 11% and reduced scanned granules by 62%.