This is cool, but this sort of proves my point to friends that Postgres isn't "production ready" out of the box, you need all kinds of tooling around it to make it so.
Show HN: Pigsty – Free RDS Alternative
11–20 of 53 posts
Re: Show HN: Pigsty – Free RDS Alternative
#12AGPL3, no thanks. Curious if there are runtime downsides to having so many extensions installed
These extensions are pre-packed and included in the local yum repo, which can be enabled by configuration. Only core extentensions are installed by default, which are: pg_repack, wal2json, postgis33, timescaledb, citus, pgvector. And the only extension activated (`CREATE EXTENSION`) by default is pg_repack. The AGPLv3 is infected by the Grafana, MinIO and citus. https://github.com/Vonng/pigsty/blob/master/docs/PGSQL-…
Personally, I like the AGPL. It means that when a place uses / extends the code, it's pretty likely they're intending on contributing back.
It's the places that go "Ewwww... AGPLv3!" that you have to wonder about.
Re: Show HN: Pigsty – Free RDS Alternative
#13Why would you ever want that many extensions?
Why would they want that many available, or installed? Those are two different questions.
Re: Show HN: Pigsty – Free RDS Alternative
#14This looks very very fragile. If all of this works, great job though.
How does it look fragile?
Re: Show HN: Pigsty – Free RDS Alternative
#15Can't say I'm following the Why? entirely.
Is this intended as a prototyping tool?
Re: Show HN: Pigsty – Free RDS Alternative
#16Earlier quoted context omitted.
These extensions are pre-packed and included in the local yum repo, which can be enabled by configuration. Only core extentensions are installed by default, which are: pg_repack, wal2json, postgis33, timescaledb, citus, pgvector. And the only extension activated (`CREATE EXTENSION`) by default is pg_repack. The AGPLv3 is infected by the Grafana, MinIO and citus. https://github.com/Vonng/pigsty/blob/master/docs/PGSQL-…
Personally, I like the AGPL. It means that when a place uses / extends the code, it's pretty likely they're intending on contributing back. It's the places that go "Ewwww... AGPLv3!" that you have to wonder about.
Until AGPL3 is tested on court I'll keep avoiding it for my day job. While I appreciate the idea, I'd rather not risk my livelihood.
My employers do contribute (however modestly) to FOSS, though typically MIT licensed.
Re: Show HN: Pigsty – Free RDS Alternative
#17This is cool, but this sort of proves my point to friends that Postgres isn't "production ready" out of the box, you need all kinds of tooling around it to make it so.
Curious which DBs are "production ready" according to you, and how you define that exactly.
Re: Show HN: Pigsty – Free RDS Alternative
#18This is cool, but this sort of proves my point to friends that Postgres isn't "production ready" out of the box, you need all kinds of tooling around it to make it so.
“Production ready” is context-dependent. If you have no need of particular features, it may make sense to not have them installed for a number of reasons.
Re: Show HN: Pigsty – Free RDS Alternative
#19This is cool, but this sort of proves my point to friends that Postgres isn't "production ready" out of the box, you need all kinds of tooling around it to make it so.
Can you speak more on what you think is missing? Looking at the repo I semi-regularly deploy grafana (which I'd argue should never be part of core postgres) and pgbackrest (I wouldn't hate having more sophisticated backup built-in). I once deployed citus for an application that needed it's special talents. In general I'd say my production use of postgres has been pretty vanilla.
Re: Show HN: Pigsty – Free RDS Alternative
#20Why would you ever want that many extensions?
They make it pretty clear that the extensions are optional. Providing support for installing a diverse set of extensions seems fine to me - everyone has different use cases