Author here. The post here is a 3rd-party translation and may drifts from original wording in a few spots. Azure and OpenAI sent me some corrections today, so I published an updated English version myself here: https://pigsty.io/blog/db/openai-pg/

Hey! It was great to meet you at the conference, it's a great writeup!

BTW for anyone who interested, I've packed pg_search and vchord_bm25 extension RPM/DEBs https://pigsty.io/ext/fts/vchord_bm25 https://pigsty.io/ext/fts/pg_search In case anyone want to benchmark by themselves. ;)

There are 351 available rpm/deb postgres extensions which can do really a lot of things: https://ext.pigsty.io/#/

I fully support ParadeDB's decision. For an open-source software company, AGPLv3 + Dual License is the most sensible choice.

If you go with Apache 2.0, you're literally doing free work for cloud vendors.

I've set up a supplementary APT/YUM repository, which builds on the official PGDG offerings. This includes 326 extensions for EL distros and 312 for Deb distros, encompassing 121 RPM packages and 133 DEB packages.

These packages support PG16 extensions across Ubuntu 22.04, Debian 12, EL8, and EL9. My efforts have been particularly focused on align OS-specific extensions across the major Linux distributions to ensure a consistent feature set.

For those who are interested, you can browse the PostgreSQL extension catalog here: (https://pigsty.io/docs/pgext/list/). Additionally, I've maintained a public Yum/Apt repository hosted on Cloudflare: https://pigsty.io/docs/pgext/usage/repo/

I'm keen to hear your thoughts and would greatly appreciate any feedback from those who have utilized these extensions.

Why not continue to use rpm/apt for building and packaging? You can reuse these packages in the Dockerfile and the image, but not the other way around.

Because of the little gains and large additional effort required in exchange.

rpm/apt are quite involved to package and the tooling is (at least compared to OCI) limited. They would provide little advantage over OCI which works on any packaging system and even OS. They don't enjoy the ecosystem advantages of OCI, despite their age.

In summary, it could be doable, but it would require much more additional effort than packaging in OCI first.

But sure, since it can be done, maybe someone wants to take on it. I won't be down for the job myself ;)

RDS is like 4~13x than EC2 on AWS, 2.3x than EC2 on aliyun. https://pigsty.io/blog/cloud/rds/

But The real cost lies on EBS, which is around 60x ~ 200x than local NVMe SSD. https://pigsty.io/blog/cloud/ebs/

https://pigsty.io/blog/cloud/bonus/

BTW, thanks for your awesome work with Pigsty :pray:

How about: PostgreSQL tuned (x47). PostgreSQL + Hydra Extension (x42) PostgreSQL + ParadeDB Extension (x10.7)

That's true for the kernel, How about extensions such as ParadeDB BM25 https://www.paradedb.com/ + PGroonga https://pgroonga.github.io/ + PG Bigm https://github.com/pgbigm/pg_bigm ?

also with pg_trgm[0] (mentioned by OP) and pgvector for semantic search you have a pretty powerful search toolkit. for example, combining them for Hybrid Search [1]

[0] https://www.postgresql.org/docs/current/pgtrgm.html

[1] Reciprocal Ranked Fusion: https://supabase.com/docs/guides/ai/hybrid-search

the difference is cached/pre-calc results in a (big on disk, expensive to compute) inverted index.. you cannot beat that at runtime

Still very limited and frankly all a bit low level primitives. Unless you are a search expert, you won't be able to do much productive with this stuff. If you are, it might fit a few use cases. But then, why limit yourself to just this stuff?

The point of that of course being that the target audience for this stuff is actually people that for whatever reason are a bit shy using the right tools for the right job here and are probably lacking a lot of expertise. The intersection of people with the expertise that would be happy with this narrow subset of functionality is just not a lot of people.

Patroni has native HA support for citus horizontal cluster since v3. Which means your can create a HA citus cluster as simple as: https://pigsty.io/docs/pgsql/config/#citus-cluster