How Smarter Databases Are Helping Robots React in Real Time

Key points

• TimescaleDB, a time-series database built on top of the widely used Postgres database software, extends Postgres to handle fast-moving industrial data without requiring a separate system.
• Doug Pagnutti, an industrial developer advocate at Tiger Data, spent more than 12 years in oil and manufacturing automation before moving into industrial software.
• Episode 254 of The Robot Report podcast explores how time-series databases improve robotics and industrial AI applications.
• Vicarious Surgical has officially shut down, and U.K.-based Humanoid closed a $152 million Series A funding round.
• Unitree says a "GPT moment" for robots, meaning a sudden broad leap in general capability, is still years away.

Every machine on a factory floor produces a stream of readings: temperatures, pressures, motor speeds, error codes. Each reading carries the exact moment it occurred. Managing that flood of tiny, time-tagged data points is a different problem from storing customer records or product catalogues, and ordinary databases weren't built for it.

That gap is what Episode 254 of The Robot Report podcast sets out to explore.

What is a time-series database, and why does it matter for robots?

A time-series database stores information in strict time order, making it fast to ask questions like "what happened in the last 30 seconds" or "show me every pressure spike from the past week." Standard databases can answer those questions, but they slow down badly as the data grows.

Guest Doug Pagnutti, an industrial developer advocate at Tiger Data, knows that slowdown first-hand. Before moving into software, he spent more than 12 years working on PLCs (programmable logic controllers, the small computers that run factory machinery), industrial robots, and SCADA systems (which monitor and control large industrial processes). He later worked at Dell EMC and VTScada before joining Tiger Data.

Tiger Data makes TimescaleDB, which sits on top of Postgres, the popular open-source database that millions of developers already use. It adds time-series capabilities, columnar storage (a way of organising data that speeds up certain queries dramatically), and automatic data partitioning (splitting large datasets into manageable chunks). Teams don't need to learn an entirely new system or move their data elsewhere. That's the pitch, anyway, and it's a credible one for shops already running Postgres.

Pagnutti discusses how factories and robotics teams connect these databases to physical sensors, how they manage data at scale, and how the same setup can run in the cloud or on local edge hardware sitting close to the machines.

What else came up in this episode?

The podcast's news segment covered three stories from the robotics space.

Chinese robotics firm Unitree told Nikkei that a "GPT moment" for robots remains years away. That's a notably cautious assessment from a company that builds and sells humanoid and quadruped robots.

Vicarious Surgical officially announced it's shutting down. We reported the Massachusetts company's plans as early as 15 July 2026, when shareholders were being asked to vote on dissolving the business and investors faced losing everything.

U.K.-based Humanoid closed a $152 million Series A round, one of the larger early-stage investments in humanoid robotics seen recently.

Common questions

Does any of this affect patients or medical robots?

Not directly in this episode, but the data challenge is identical in medical robotics. Surgical and rehabilitation robots produce dense streams of time-stamped sensor readings that need fast, reliable storage, and the approaches discussed here apply across the field.

Do I need to understand databases to follow this?

No. The conversation targets engineers who already work with industrial systems, but the core idea is simple: as machines get smarter and more connected, the software storing their data needs to keep pace.