5 ms·
Other related projects: * PGXN (https://pgxn.org/ https://pgxn.org/ - the original Postgres community extension repository, though more "old school") * Trunk
by lfittl 3y ago
Other related projects:
* PGXN (https://pgxn.org/ https://pgxn.org/ - the original Postgres community extension repository, though more "old school")
* Trunk by Tembo (https://github.com/tembo-io/trunk https://github.com/tembo-io/trunk - very similar to pgxman, but using the more liberal Postgres BSD-style license)
Additionally its important to mention that many popular extensions are already packaged as part of the Postgres YUM and Apt repositories (https://wiki.postgresql.org/wiki/Apt https://wiki.postgresql.org/wiki/Apt and https://yum.postgresql.org/ https://yum.postgresql.org/).
I would generally recommend using the upstream repository packages directly, since they are tested/updated with each major release, and their maintainers are proactive in reaching out to extension maintainers that need to update their extension due to upstream code changes.
- kiwicopple 3y agoAlso database.dev, specifically for Trusted Language Extensions: https://supabase.com/blog/dbdev https://supabase.com/blog/dbdev
- owenthereal 3y ago> I would generally recommend using the upstream repository packages directly, since they are tested/updated with each major release, and their maintainers are proactive in reaching out to extension maintainers that need to update their extension due to upstream code changes. Not all extensions have an upstream repository and built debian/yum packages. At Hydra, we test all published in https://github.com/pgxman/buildkit https://github.com/pgxman/buildkit which is available from our registry.
- rywalker 3y agoWe have some exciting news re: Trunk to announce in January — taking the project to the next level. Thanks for mention :)