{"ok":true,"trend":{"id":633512,"platform":"hn","region":"global","key":"paradedb search performance improvements","title":"ParadeDB Search Performance Improvements","url":"https://www.paradedb.com/blog/opening-a-closed-tin","first_seen":"2026-10-01T17:20:39.663052Z","last_seen":"2026-10-01T21:50:40.101025Z","last_rank":21,"peak_rank":19,"last_volume":54,"peak_volume":54,"seen_count":19,"score":0.89828125,"category_hint":null,"section":null,"category":null,"summary":"ParadeDB, the open-source search platform built on PostgreSQL, has published details of significant performance improvements to its search engine. The post, titled 'Opening a Closed Tin', explains the technical work behind the speed gains. Developers on Hacker News are discussing the changes, with interest in what the improvements mean for search workloads on Postgres.","why":"The developer community is discussing the newly announced technical improvements and their implications for Postgres-based search.","tone":"positive","entities":["ParadeDB","PostgreSQL"],"summarized_at":"2026-10-01T23:23:31.741567Z","meta":{"lang":"en","link":"https://www.paradedb.com/blog/opening-a-closed-tin","hn_id":"49924275","comments":9},"nw":null,"promo":null,"kind":null,"importance":null,"hidden":false,"hide_reason":null,"judged_at":null,"title_en":"ParadeDB Announces Search Performance Improvements","timeline":[{"captured_at":"2026-10-01T17:20:39.663052Z","rank":28,"volume":5},{"captured_at":"2026-10-01T17:35:39.766452Z","rank":28,"volume":7},{"captured_at":"2026-10-01T17:50:39.660663Z","rank":29,"volume":9},{"captured_at":"2026-10-01T18:05:39.803819Z","rank":25,"volume":24},{"captured_at":"2026-10-01T18:20:40.200081Z","rank":25,"volume":28},{"captured_at":"2026-10-01T18:35:40.060037Z","rank":24,"volume":30},{"captured_at":"2026-10-01T18:50:39.735313Z","rank":24,"volume":34},{"captured_at":"2026-10-01T19:05:39.680983Z","rank":23,"volume":36},{"captured_at":"2026-10-01T19:20:39.666894Z","rank":23,"volume":38},{"captured_at":"2026-10-01T19:35:39.803724Z","rank":23,"volume":39},{"captured_at":"2026-10-01T19:50:39.694587Z","rank":21,"volume":40},{"captured_at":"2026-10-01T20:05:39.666469Z","rank":25,"volume":44},{"captured_at":"2026-10-01T20:20:39.609658Z","rank":23,"volume":46},{"captured_at":"2026-10-01T20:35:39.683928Z","rank":21,"volume":50},{"captured_at":"2026-10-01T20:50:39.628499Z","rank":19,"volume":53},{"captured_at":"2026-10-01T21:05:39.768418Z","rank":21,"volume":54},{"captured_at":"2026-10-01T21:20:39.712133Z","rank":23,"volume":54},{"captured_at":"2026-10-01T21:35:39.634011Z","rank":23,"volume":54},{"captured_at":"2026-10-01T21:50:40.101025Z","rank":21,"volume":54}],"posts":[{"platform":"hn","url":"https://news.ycombinator.com/item?id=49924275","author":"craigkerstiens","title":"ParadeDB Search Performance Improvements","snippet":null,"posted_at":"2026-10-01T17:05:01Z","likes":54}],"elsewhere":[],"window":"7d"}}