# Timescale

Insights, product updates, and tips from TigerData (Creators of TimescaleDB) engineers on Postgres, time series & AI. IoT, crypto, and analytics tutorials & use cases.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## You Didn't Choose Your Split Architecture. You Accumulated It.

DevFeed: [You Didn't Choose Your Split Architecture. You Accumulated It.](<https://devfeed.tech/articles/you-didn-t-choose-your-split-architecture-you-accumulated-it-127486.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/split-architecture-second-database>)

Author: Matty Stratton

Published: 2026-11-10T15:00:26Z

Content type: article

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [architecture-components](<https://devfeed.tech/topics/architecture-components.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [copy](<https://devfeed.tech/tags/copy.md>), [database](<https://devfeed.tech/tags/database.md>), [split](<https://devfeed.tech/tags/split.md>)

### AI overview

A second database can emerge through a series of reasonable fixes rather than a deliberate architecture decision, with costs arriving along the way. The description urges answering three questions before adding another copy, but does not specify what they are.

### Source excerpt

A second database rarely arrives as a decision. It arrives as a series of reasonable fixes, and the bill arrives anyway.

## Adaptive Integer Compression in TimescaleDB: Built for the Read Path

DevFeed: [Adaptive Integer Compression in TimescaleDB: Built for the Read Path](<https://devfeed.tech/articles/adaptive-integer-compression-in-timescaledb-built-for-the-read-path-106829.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/adaptive-integer-compression-aic-in-timescaledb>)

Author: David Beck

Published: 2026-10-29T12:02:58Z

Content type: article

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [Compression](<https://devfeed.tech/topics/compression.md>), [Encoding](<https://devfeed.tech/topics/encoding.md>)

Tags: [adaptive](<https://devfeed.tech/tags/adaptive.md>), [compression](<https://devfeed.tech/tags/compression.md>), [encoding](<https://devfeed.tech/tags/encoding.md>), [fast](<https://devfeed.tech/tags/fast.md>), [foreign-keys](<https://devfeed.tech/tags/foreign-keys.md>), [integer-compression](<https://devfeed.tech/tags/integer-compression.md>), [query](<https://devfeed.tech/tags/query.md>), [small](<https://devfeed.tech/tags/small.md>), [sources](<https://devfeed.tech/tags/sources.md>), [status](<https://devfeed.tech/tags/status.md>), [tables](<https://devfeed.tech/tags/tables.md>), [time-series](<https://devfeed.tech/tags/time-series.md>), [timescaledb](<https://devfeed.tech/tags/timescaledb.md>)

### AI overview

Adaptive Integer Compression (AIC) selects an encoding for each block from options that decompress quickly. This addresses tables where integers include status codes, foreign keys, or interleaved sources, often arriving in small batches--data that DeltaDelta may not suit as well as time-series-shaped integers. The excerpt says queries reading this data must decompress it first; it does not provide performance measurements or describe the available encodings.

### Source excerpt

DeltaDelta suits time-series-shaped integers. Real tables also hold status codes, foreign keys and interleaved sources, often in small batches. Every query that reads that data has to decompress it first, so AIC picks the encoding per block, and only from encodings that decompress fast.

## Building an Ingest Safety Monitor for Your IIoT Pipeline in SQL

DevFeed: [Building an Ingest Safety Monitor for Your IIoT Pipeline in SQL](<https://devfeed.tech/articles/building-an-ingest-safety-monitor-for-your-iiot-pipeline-in-sql-88675.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/building-ingest-safety-monitor-iiot-pipeline-sql>)

Author: John Shi

Published: 2026-10-16T12:55:08Z

Content type: tutorial

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

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

Tags: [headroom](<https://devfeed.tech/tags/headroom.md>), [iiot](<https://devfeed.tech/tags/iiot.md>), [monitor](<https://devfeed.tech/tags/monitor.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [replica](<https://devfeed.tech/tags/replica.md>), [replica-lag](<https://devfeed.tech/tags/replica-lag.md>), [safety](<https://devfeed.tech/tags/safety.md>), [sql](<https://devfeed.tech/tags/sql.md>), [volume](<https://devfeed.tech/tags/volume.md>), [wal](<https://devfeed.tech/tags/wal.md>)

### AI overview

The article describes an SQL-based safety monitor for an IIoT ingestion pipeline. It recommends sampling WAL volume, replica lag, and dead tuples every minute and calculating a headroom percentage that can trigger alerts.

### Source excerpt

Ingest fails suddenly, not gradually. Sample WAL volume, replica lag, and dead tuples every minute, and get one headroom percentage you can alert on.

## Announcing pg\_vectorsearch: Scalable Open-Source Vector Search in PostgreSQL

DevFeed: [Announcing pg\_vectorsearch: Scalable Open-Source Vector Search in PostgreSQL](<https://devfeed.tech/articles/announcing-pg-vectorsearch-scalable-open-source-vector-search-in-postgresql-86110.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/announcing-pg_vectorsearch-scalable-open-source-vector-search-postgresql>)

Author: Erik Nordström

Published: 2026-10-13T14:40:36Z

Content type: release

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [PostgreSQL](<https://devfeed.tech/topics/postgresql.md>), [Open Source](<https://devfeed.tech/topics/open-source.md>)

Tags: [announcements-releases](<https://devfeed.tech/tags/announcements-releases.md>), [hnsw](<https://devfeed.tech/tags/hnsw.md>), [index](<https://devfeed.tech/tags/index.md>), [pg-vectorsearch](<https://devfeed.tech/tags/pg-vectorsearch.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [vectorsearch](<https://devfeed.tech/tags/vectorsearch.md>)

### AI overview

pg_vectorsearch is a new open-source PostgreSQL extension with a PRISM index. It reportedly serves 100 million vectors in 6 ms, uses four times less RAM than HNSW, and builds in under two hours.

### Source excerpt

pg_vectorsearch is a new open-source Postgres extension. Its PRISM index serves 100M vectors in 6 ms on 4x less RAM than HNSW, with builds in under 2 hours.

## Measuring How Fast Your IIoT Queries Are Degrading

DevFeed: [Measuring How Fast Your IIoT Queries Are Degrading](<https://devfeed.tech/articles/measuring-how-fast-your-iiot-queries-are-degrading-84198.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/measuring-how-fast-iiot-queries-degrading>)

Author: John Shi

Published: 2026-10-09T12:00:40Z

Content type: tutorial

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [database-optimization](<https://devfeed.tech/topics/database-optimization.md>), [performance-optimization](<https://devfeed.tech/topics/performance-optimization.md>)

Tags: [iiot](<https://devfeed.tech/tags/iiot.md>), [industry](<https://devfeed.tech/tags/industry.md>), [latency](<https://devfeed.tech/tags/latency.md>), [measuring](<https://devfeed.tech/tags/measuring.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [target](<https://devfeed.tech/tags/target.md>)

### AI overview

Track query latency against row count, fit a curve, and estimate when an IIoT query will exceed its target.

### Source excerpt

Stop waiting for the dashboard to get slow. Record latency against row count, fit the curve, and get a date when your query breaches its target.

## Continuous Aggregate Refresh Policies for Solar and Wind SCADA Data: Choosing the Right Policy Shape

DevFeed: [Continuous Aggregate Refresh Policies for Solar and Wind SCADA Data: Choosing the Right Policy Shape](<https://devfeed.tech/articles/continuous-aggregate-refresh-policies-for-solar-and-wind-scada-data-choosing-the-right-policy-shape-66783.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/continuous-aggregate-refresh-policies-solar-wind-scada>)

Author: Damaso Sanoja

Published: 2026-10-07T12:14:21Z

Content type: tutorial

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>), [streaming data analytics](<https://devfeed.tech/topics/streaming-data-analytics.md>)

Tags: [continuous](<https://devfeed.tech/tags/continuous.md>), [data](<https://devfeed.tech/tags/data.md>), [iot](<https://devfeed.tech/tags/iot.md>), [timescaledb](<https://devfeed.tech/tags/timescaledb.md>)

### AI overview

The document outlines five refresh policy shapes for solar and wind SCADA data: frequent, daily, hierarchical, retention-aware, and manual. It recommends choosing a shape to fit each job.

### Source excerpt

Five refresh policy shapes for solar and wind SCADA: frequent, daily, hierarchical, retention-aware, and manual. Pick the one that fits each job.

## Normalizing a Wide Well and Pipeline Telemetry Table Without Re-Ingesting History

DevFeed: [Normalizing a Wide Well and Pipeline Telemetry Table Without Re-Ingesting History](<https://devfeed.tech/articles/normalizing-a-wide-well-and-pipeline-telemetry-table-without-re-ingesting-history-62632.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/normalizing-wide-well-pipeline-telemetry-table-without-re-ingesting-history>)

Author: Damaso Sanoja

Published: 2026-09-30T13:58:45Z

Content type: tutorial

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [table-partitioning](<https://devfeed.tech/topics/table-partitioning.md>)

Tags: [iot](<https://devfeed.tech/tags/iot.md>), [pipeline](<https://devfeed.tech/tags/pipeline.md>), [table](<https://devfeed.tech/tags/table.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [wide](<https://devfeed.tech/tags/wide.md>)

### AI overview

The article describes reshaping a wide oilfield SCADA telemetry table into a narrow hypertable with tag metadata, while keeping the change in place and dashboards running without re-ingesting historical data.

### Source excerpt

Reshape a wide oilfield SCADA table into a narrow hypertable plus tag metadata, in place, with dashboards running and history left where it is.

## Agent Memory Is a Search Problem, Not a Storage Problem

DevFeed: [Agent Memory Is a Search Problem, Not a Storage Problem](<https://devfeed.tech/articles/agent-memory-is-a-search-problem-not-a-storage-problem-61866.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/agent-memory-search-problem-not-storage-problem>)

Author: Matvey Arye

Published: 2026-09-29T13:00:52Z

Content type: article

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [AI-driven information retrieval](<https://devfeed.tech/topics/ai-driven-information-retrieval.md>), [Retrieval Augmented Generation (RAG)](<https://devfeed.tech/topics/retrieval-augmented-generation-rag.md>)

Tags: [agent-memory](<https://devfeed.tech/tags/agent-memory.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [postgres](<https://devfeed.tech/tags/postgres.md>), [search](<https://devfeed.tech/tags/search.md>)

### AI overview

The document reports that one Postgres table and three search tools, without fact extraction, graphs, or a memory manager, scored F1 0.665 on LoCoMo.

### Source excerpt

No fact extraction, no graphs, no memory manager. One Postgres table and three search tools scored F1 0.665 on LoCoMo.

## 41 Experiments in 6 Days: What the Human Was Actually For

DevFeed: [41 Experiments in 6 Days: What the Human Was Actually For](<https://devfeed.tech/articles/41-experiments-in-6-days-what-the-human-was-actually-for-61167.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/41-experiments-6-days-what-human-was-for>)

Author: Matvey Arye

Published: 2026-09-28T12:47:44Z

Content type: article

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [AI Engineering](<https://devfeed.tech/topics/ai-engineering.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [ML model versioning](<https://devfeed.tech/topics/ml-model-versioning.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [claude](<https://devfeed.tech/tags/claude.md>), [experiments](<https://devfeed.tech/tags/experiments.md>), [metrics](<https://devfeed.tech/tags/metrics.md>)

### AI overview

Across 41 experiments conducted over six days, LoCoMo memory's F1 score increased from 0.392 to 0.666. Claude wrote the code, while a human identified misleading metrics.

### Source excerpt

41 experiments in 6 days took LoCoMo memory from F1 0.392 to 0.666. Claude wrote the code; the human caught the metrics that were lying.

## Sizing Your IIoT Table Before You Deploy

DevFeed: [Sizing Your IIoT Table Before You Deploy](<https://devfeed.tech/articles/sizing-your-iiot-table-before-you-deploy-60002.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/sizing-your-iiot-table-before-you-deploy>)

Author: John Shi

Published: 2026-09-25T11:57:49Z

Content type: article

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

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

Tags: [deploy](<https://devfeed.tech/tags/deploy.md>), [iiot](<https://devfeed.tech/tags/iiot.md>), [iot](<https://devfeed.tech/tags/iot.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [schema](<https://devfeed.tech/tags/schema.md>), [sensor](<https://devfeed.tech/tags/sensor.md>), [test](<https://devfeed.tech/tags/test.md>)

### AI overview

A guide to sizing an IIoT table before deployment by measuring row storage, projecting 631 billion sensor readings, and testing ingest capacity before schema review.

### Source excerpt

A 20-byte sensor reading costs 95.6 on disk. Measure bytes per row, project 631 billion rows, and test your ingest ceiling before the schema review.

## Knowing When Your Composite Index Earns Its Write Cost

DevFeed: [Knowing When Your Composite Index Earns Its Write Cost](<https://devfeed.tech/articles/knowing-when-your-composite-index-earns-its-write-cost-55018.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/knowing-when-composite-index-earns-write-cost>)

Author: NanoHertz Communications

Published: 2026-09-18T12:49:15Z

Content type: tutorial

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

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

Tags: [audit](<https://devfeed.tech/tags/audit.md>), [cost](<https://devfeed.tech/tags/cost.md>), [indexes](<https://devfeed.tech/tags/indexes.md>), [insert](<https://devfeed.tech/tags/insert.md>), [postgresql](<https://devfeed.tech/tags/postgresql.md>), [postgresql-performance](<https://devfeed.tech/tags/postgresql-performance.md>), [queries](<https://devfeed.tech/tags/queries.md>), [write](<https://devfeed.tech/tags/write.md>)

### AI overview

A guide to evaluating whether composite indexes justify their write cost by comparing insert overhead with query benefits and auditing existing indexes.

### Source excerpt

Composite indexes charge every insert and pay back only some queries. Four steps to price both sides and audit the indexes you already run.

## How Meshtastic Metrics Exporter Turned Eight Prometheus Queries Into One with Tiger Data

DevFeed: [How Meshtastic Metrics Exporter Turned Eight Prometheus Queries Into One with Tiger Data](<https://devfeed.tech/articles/how-meshtastic-metrics-exporter-turned-eight-prometheus-queries-into-one-with-tiger-data-42188.md>)

Original publisher: [Read original article](<https://www.tigerdata.com/blog/meshtastic-metrics-exporter-case-study-tiger-data>)

Author: Andrew Stebbins

Published: 2026-09-16T12:44:25Z

Content type: article

Language: en

Sources: [Timescale](<https://devfeed.tech/sources/timescale.md>)

Topics: [meshtastic](<https://devfeed.tech/topics/meshtastic.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [Database](<https://devfeed.tech/topics/database.md>), [data](<https://devfeed.tech/topics/data.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [mesh](<https://devfeed.tech/tags/mesh.md>), [meshtastic](<https://devfeed.tech/tags/meshtastic.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [radio](<https://devfeed.tech/tags/radio.md>), [series](<https://devfeed.tech/tags/series.md>), [timescaledb](<https://devfeed.tech/tags/timescaledb.md>)

### AI overview

A case study describes how Meshtastic Metrics Exporter consolidated eight Prometheus queries into one Postgres database, reducing more than 500,000 metric series for 10,000 mesh radio nodes.

### Source excerpt

Meshtastic Metrics Exporter reduced 500K+ Prometheus metric series to one Postgres database: consolidated eight queries into one with Tiger Data for 10,000 mesh radio nodes.