Re:Why Postgres Extensions should be packaged and distribute...
by justinclift on Friday April 05, 2024 @08:53PM
(#39949016)
> ... PostgreSQL package.
Is it able to automatically upgrade people from older PG versions?
If not, the MIT licensed code from here might be worth looking through and grabbing ideas from? :)
https://github.com/pgautoupgrade/docker-pgautoupgrade
Specifically the scripting here is the bulk of it, the majority of the other stuff is just the existing docker entrypoint code from the official Docker PG container:
https://github.com/pgautoupgrade/docker-pgautoupgrade/blob/0...
Re:Why Postgres Extensions should be packaged and distribute...
by justinclift on Friday April 05, 2024 @08:57PM
(#39949035)
Oh, you'll probably want to use "make install-world" rather than "make install". The "-world" version also includes many PG extensions when it runs, which is likely beneficial. :)
https://codeberg.org/stagex/stagex/src/branch/main/packages/...
Built and signed by multiple people and entirely distro agnostic. You can even build with your pick of several OCI engines on several operating systems so maximally portable too.
If extensions are packaged similarly it will sure make my life easier integrating them.
If you are going to package with only one standard, OCI is the most portable and flexible choice today IMO.
https://codeberg.org/stagex/stagex/src/branch/main/packages/...