ParadeDB is Postgres for search and analytics. As Postgres continues to rise in popularity, the "Just Use Postgres'' movement is getting stronger and stronger. Yet there are still things that standard Postgres doesn't do well, and advanced search and analytics functionality is near the top of the list.

The ParadeDB team provides a pair of Postgres extensions. The first, pg_search, brings a more performant and full-featured search experience to Postgres. It uses Tantivy (think: Lucene but Rust) as the search engine and provides advanced ranking and querying functionality. The second, pg_lakehouse, allows you to perform large analytical queries over object store data. Together, these provide compelling new features wrapped in a familiar operational package.

Philippe Noël is one of the founders of ParadeDB. In this episode, we talk about why these extensions were needed, why the 'Just Use Postgres' movement exists, and where ParadeDB fits in your architecture.

Follow Philippe: https://x.com/philippemnoel

Follow Alex: https://x.com/alexbdebrie

Follow Sean: https://x.com/seanfalconer

Check Out ParadeDB: https://www.paradedb.com/

Timestamps

01:50:18 Intro

04:30:23 Where does seach on Postgres fall down?

05:33:09 BM25 and TF-IDF

07:23:03 Postgres Tipping Point

10:05:08 Tantivy

11:50:14 Tantivy vs Lucene

13:07:06 vs ZomboDB

15:35:21 Just Use Postgres for Everything?

17:57:17 Developing a Postgres Extension

19:26:03 Arvid's Problem

20:27:08 Postgres and Log Data

23:28:01 Separate OLTP and Search Instances

28:32:01 Search Nodes vs OLTP Nodes

30:02:12 ParadeDB Analytics

35:27:05 Hosted Service

39:03:15 Stumbling upon the Idea

39:51:22 Community

41:01:15 Getting Started with ParadeDB