philippemnoel

Hi there! Yes, that is a problem. We have an issue tracking it here: https://github.com/paradedb/paradedb/issues/6007

ParadeDB (YC S23, https://paradedb.com) | Database Internals Engineers, Platform Engineers | Remote or hybrid in San Francisco | Full-time

ParadeDB is a Postgres extension that delivers state-of-the-art search in Postgres. Our customers, including Alibaba Cloud, BILT Rewards, Modern Treasury (YC S18), and many others, rely on us to deliver the performance and feature set of dedicated vector databases/Elasticsearch natively in Postgres, simplifying their stack and day-to-day operations.

If you like systems, this might be for you. We're a team of 10, a Series A company based in SF but distributed across North America. We're hiring for database internals work (e.g., building the database in Rust) and distributed systems work (e.g., building the database-as-a-service platform in Go).

We're open-source at https://github.com/paradedb/paradedb.

Our technical blog: https://www.paradedb.com/blog

More info on roles: https://paradedb.notion.site/

As for the AGPL question, our primary goal with this license is to protect ourselves from hyperscalers and avoid fragmenting the community. You can read more about it here: https://news.ycombinator.com/item?id=41227172

We have many community contributors (150 and counting) who submit PRs and many users who open issues. We love them!

We're well aware that our external contributors use AI (we do too!), and we fiercely guard our product against AI slop. We ask that external contributors understand the changes they are making, and we frequently close PRs unmerged if they look like slop.

ParadeDB developer here. BM25 FTS is becoming available on more cloud platforms, but ParadeDB is much more than that now. We'll have blog posts over the next few months detailing our work on aggregates, JOINs, filters, etc.

ParadeDB/pg_search developer here. Yes, we started the project before LLMs. Moreover, our project is now much more than just full-text search.

I do agree with the sentiment here that many of the other FTS-in-Postgres projects in recent years have been heavily enabled by vibe coding.

As a Canadian, I find this unbelievably good news. Canada, the EU, and other middle powers need to unite. Stronger together, while preserving what makes each country unique.

The notion that "every human interaction is worth preserving" is probably not right, and Waymos are showcasing this. As the author mentions, many people don't enjoy the forced small talk with Uber drivers. Interacting with people from different backgrounds and perspectives is important, but I doubt the forced interactions like taxi rides are where we were getting those until day.

My English fails me again :'). Thank you for the correction!

You're right that vanilla Postgres doesn't come close to replacing Elastic. There are efforts to resolve this, though, like ParadeDB: https://github.com/paradedb/paradedb (disclaimer: I work for ParadeDB)

Enfin!!

There is significant work happening in the PostgreSQL ecosystem to make "use a single system to run everything" possible. ParadeDB is one such system pushing on full-text/vector search, with some light aggregations, at the index level. There is also work being done by DuckDB folks with pg_duckdb and others like Xata. (disclaimer: I work at ParadeDB)

Let's go. Very bullish on PgDog. Lev understands this space better than anyone else. If you are sharding Postgres, you should talk to him.

I've been wanting this for so long. This is so clever.

Slightly concerned Apple would patch this by preventing others from using the same bundle identifier as their official apps, though?

Writing code was never the job. Writing code was always a means to the job. This is why people hire "software engineers", not merely "programmers".

ParadeDB maintainer here :). We would happily make it available on Azure (and all other cloud providers!) if there were a way for us to earn a living in doing so.

Fyi, we are in discussion with some hyperscalers on making this possible.

ParadeDB (YC S23, https://paradedb.com) | Database Internals Engineers, Distributed Systems Engineers | Remote or hybrid in San Francisco | Full-time

ParadeDB is a Postgres extension that delivers state-of-the-art search in Postgres. Our customers, including Alibaba Cloud, BILT Rewards, Modern Treasury (YC S18), and many others, rely on us to deliver the performance and feature set of dedicated vector databases/Elasticsearch natively in Postgres, simplifying their stack and day-to-day operations.

If you like systems, this might be for you. We're a team of 10, a Series A company based in SF but distributed across North America. We're hiring for database internals work (e.g., building the database in Rust) and distributed systems work (e.g., building the database-as-a-service platform in Go).

We're open-source at https://github.com/paradedb/paradedb.

Our technical blog: https://www.paradedb.com/blog

More info on roles: https://paradedb.notion.site/

This a 100 times^. The Postgres ecosystem is remarkable and has managed to strike the balance between OSS and commercial successes in a way that most infra verticals have not.

We (ParadeDB) use Barman via CloudNativePG for almost all our deployments. It's been solid, although I've had a few complaints about 1) inability to set S3 storage classes, 2) slow upload for very large databases.

Nonetheless, very happy to see this project on the front page of HN!

ParadeDB (YC S23, https://paradedb.com) | Database Internals Engineers | Remote or hybrid in San Francisco | Full-time

ParadeDB is a Postgres extension that delivers state-of-the-art search in Postgres. Our customers, including Alibaba Cloud, BILT Rewards, Modern Treasury (YC S18) and many others, rely on us to deliver them the performance and feature set of dedicated vector databases/Elasticsearch natively in Postgres, to simplify their stack and day-to-day operations.

If you like systems, this might be for you. We're a team of 11, Series A company based in SF but distributed across North America.

We're open source at: https://github.com/paradedb/paradedb. Our technical blog: https://www.paradedb.com/blog More info on roles: https://paradedb.notion.site/

https://github.com/paradedb/paradedb -- Full-text & vector search natively in Postgres

Good catch, thank you both -- fixed!

Under the hood, ParadeDB is built by integrating Tantivy (a Lucene-inspired Rust search library) inside Postgres. This is to say: I agree with you -- We're not trying to claim that Postgres itself is an alternative to Lucene, but rather that something like Lucene can be integrated inside Postgres so that you can get the power of both in a single system (or in a cluster of Postgres instances)

(ParadeDB maintainer here) Yes! We've already built some faster analytics in Postgres, and have a lot more coming. Here's some relevant context in case you're curious: https://www.paradedb.com/blog/faceting

Anytime! We have some vector search work coming in the next few weeks/months that I expect you'll find interesting. Stay tuned :)

We just made a blueprint for it! https://github.com/paradedb/render-blueprint

One-click deploy with Render, and we're directly in contact with the core team to get it added to their official docs. I hear the PR is up internally :)

(ParadeDB maintainer here). This is super cool. Congrats on the project, and I'm excited to see ParadeDB be used to power this kind of use case. If there's anything else you need to ship Omni, don't hesitate to reach out to me!

That's true. For this reason, most modern search engines support language-aware stemming and tokenization. Popular tokenizers for CJK languages include Lindera and Jieba.

We (ParadeDB) use a search library called Tantivy under the hood, which supports stemming in Finnish, Danish and many other languages: https://docs.paradedb.com/documentation/token-filters/stemmi...

ParadeDB | https://paradedb.com | SF Onsite + Remote | Full-Time | Rust Database Engineers

ParadeDB is an alternative to Elasticsearch built on Postgres. We're building a Postgres extension in Rust that offers a new index type optimized for full-text search and aggregate/analytics workloads. We solve three problems with Elasticsearch today:

- Lack of read-after-writes guarantees

- Lack of JOINs

- Infrastructure complexity & cost due to syncing Postgres and Elastic.

We're open-source, and our repository is available at https://github.com/paradedb/paradedb. We're a Series A team of 8 distributed across the US and Canada. Most folks on our team have 10+ years of experience in database internals at companies like Twitter, MongoDB, Oracle, Instacart, etc.

You can find our roles and the profiles of our team members here: https://paradedb.notion.site

If you know Rust and/or have experience working on DB internals and want to work on cool systems problems, shoot us a note. We hire with conviction, have lots of room to grow, and exciting technical problems to solve. My email is phil@paradedb.com.

How so? Many popular projects are AGPL. MinIO, Grafana, etc.

We wrote about this here: https://www.paradedb.com/blog/agpl