1. X
  2. TimescaleDB (by Tiger Data)
Log inSign up
TimescaleDB (by Tiger Data)
5,903 posts
Image
user avatar
TimescaleDB (by Tiger Data)
@TimescaleDB
Now @tigerdatabase. The modern cloud platform built on PostgreSQL for time series, events, and analytics (and vectors too). ⭐️ - github.com/timescale.
🌎 Employees Worldwide
tigerdata.com
Joined July 2015
459
Following
9,135
Followers
RepliesRepliesMediaMedia

Log in or sign up for X

See what’s happening and join the conversation

Continue with phone
or
Log in with username or email
Terms·Privacy·Cookies·Accessibility·Ads Info·© 2026 X Corp.
  • Pinned
    user avatar
    TimescaleDB (by Tiger Data)
    @TimescaleDB
    Jun 17, 2025
    🐯 Timescale is now TigerData! 🚀 Eight years ago, we started as a PostgreSQL-based time-series database. But innovation never stands still—and neither have we. Today, we proudly unveil @TigerDatabase, marking our evolution into the fastest and most powerful PostgreSQL
    Image
    GIF
    7.1K
  • user avatar
    TimescaleDB (by Tiger Data)
    @TimescaleDB
    Jul 30
    Time-series analytics at scale creates operational friction. Refreshes block each other, configuration changes require rebuilds, new aggregates mean recomputing entire rollups. TimescaleDB 2.28 changes that. 1/5
    365
  • user avatar
    TimescaleDB (by Tiger Data)
    @TimescaleDB
    Jul 29
    Your factory generates millions of data points per hour. Your cloud bills are crushing. Your dashboards show yesterday's alarms. This is an architecture problem, not a tool problem. New: @michaelfreedman on the Energy Tech Podcast talks edge-to-cloud operational data.
    Image
    538
  • user avatar
    TimescaleDB (by Tiger Data)
    @TimescaleDB
    Jul 29
    Millions of sensor readings per hour. You're told you need a second database for analytics. Not true. Doug Pagnutti explains how to keep it all on Postgres with time-series primitives. 🎧 Listen here: therobotreport.com/how-time-serie…
    Image
    415
  • user avatar
    TimescaleDB (by Tiger Data)
    @TimescaleDB
    Jul 28
    Vector search in Postgres is simple until your data grows. Then it's an index design problem. Four constraints decide the right index: memory, recall, write volume, filter selectivity. HNSW, IVFFlat, StreamingDiskANN, or hybrid with BM25. Decision guide: tsdb.co/v9n4ire4
    Image
    468
  • See @TimescaleDB's full profile

    Sign up
    Log in
Advertisement
Advertisement