Provide RPM packages for EL8 about paradedb HOT 12 OPEN

No, hand made. Bump extenions to the latest version when new version of Pigsty is about to release.

git clone --recursive https://github.com/paradedb/paradedb.git
cd ~/paradedb; git checkout v0.6.1;

export PATH=/usr/pgsql-16/bin:/root/.cargo/bin:/pg/bin:/usr/share/Modules/bin:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/home/vagrant/.cargo/bin;
cd ~/paradedb/pg_search; HTTPS_PROXY=http://192.168.0.104:8118 cargo pgrx package; 
cd ~/paradedb/pg_analytics; HTTPS_PROXY=http://192.168.0.104:8118 cargo pgrx package; 

export PATH=/usr/pgsql-15/bin:/root/.cargo/bin:/pg/bin:/usr/share/Modules/bin:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/home/vagrant/.cargo/bin;
cd ~/paradedb/pg_search; cargo pgrx package -vvv; 
cd ~/paradedb/pg_analytics; cargo pgrx package  -vvv;

rm -rf ~/rpmbuild/SOURCES/pg_search_16;      cp -r ~/paradedb/target/release/pg_search-pg16      ~/rpmbuild/SOURCES/pg_search_16;
rm -rf ~/rpmbuild/SOURCES/pg_analytics_16;   cp -r ~/paradedb/target/release/pg_analytics-pg16   ~/rpmbuild/SOURCES/pg_analytics_16;
rm -rf ~/rpmbuild/SOURCES/pg_search_15;      cp -r ~/paradedb/target/release/pg_search-pg15      ~/rpmbuild/SOURCES/pg_search_15;
rm -rf ~/rpmbuild/SOURCES/pg_analytics_15;   cp -r ~/paradedb/target/release/pg_analytics-pg15   ~/rpmbuild/SOURCES/pg_analytics_15;

cd ~/rpmbuild/SPECS;
make pg_search pg_analytics;

rpmbuild --without debuginfo --define "pgmajorversion 16" -ba ~/rpmbuild/SPECS/pg_search.spec
rpmbuild --without debuginfo --define "pgmajorversion 16" -ba ~/rpmbuild/SPECS/pg_analytics.spec
rpmbuild --without debuginfo --define "pgmajorversion 15" -ba ~/rpmbuild/SPECS/pg_search.spec
rpmbuild --without debuginfo --define "pgmajorversion 15" -ba ~/rpmbuild/SPECS/pg_analytics.spec

Got it. Thanks for sharing. Assuming we can run rpmbuild on Ubuntu, I'm happy to pick this up and support these other platforms. I'll look into it next week

from paradedb.

I've started taking a look at this as part of a PR to fix another user issue, will keep you posted

from paradedb.

What Provide pg_search & pg_analytics RPM packages for EL8, EL9

Why EL8, EL9 is widely used, especially in enterprise scenarios

How We already have building & packaing templates for pg_search and pg_analytics

Just add them to the project CI/CD pipeline and release rpm @ the release page

And it would be great to provide debian 11/12 packages too.

Does Pigsty build to RPM on the GitHub Actions runners?

from paradedb.

No, hand made. Bump extenions to the latest version when new version of Pigsty is about to release.

git clone --recursive https://github.com/paradedb/paradedb.git
cd ~/paradedb; git checkout v0.6.1;

export PATH=/usr/pgsql-16/bin:/root/.cargo/bin:/pg/bin:/usr/share/Modules/bin:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/home/vagrant/.cargo/bin;
cd ~/paradedb/pg_search; HTTPS_PROXY=http://192.168.0.104:8118 cargo pgrx package; 
cd ~/paradedb/pg_analytics; HTTPS_PROXY=http://192.168.0.104:8118 cargo pgrx package; 

export PATH=/usr/pgsql-15/bin:/root/.cargo/bin:/pg/bin:/usr/share/Modules/bin:/usr/lib64/ccache:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin:/home/vagrant/.cargo/bin;
cd ~/paradedb/pg_search; cargo pgrx package -vvv; 
cd ~/paradedb/pg_analytics; cargo pgrx package  -vvv;

rm -rf ~/rpmbuild/SOURCES/pg_search_16;      cp -r ~/paradedb/target/release/pg_search-pg16      ~/rpmbuild/SOURCES/pg_search_16;
rm -rf ~/rpmbuild/SOURCES/pg_analytics_16;   cp -r ~/paradedb/target/release/pg_analytics-pg16   ~/rpmbuild/SOURCES/pg_analytics_16;
rm -rf ~/rpmbuild/SOURCES/pg_search_15;      cp -r ~/paradedb/target/release/pg_search-pg15      ~/rpmbuild/SOURCES/pg_search_15;
rm -rf ~/rpmbuild/SOURCES/pg_analytics_15;   cp -r ~/paradedb/target/release/pg_analytics-pg15   ~/rpmbuild/SOURCES/pg_analytics_15;

cd ~/rpmbuild/SPECS;
make pg_search pg_analytics;

rpmbuild --without debuginfo --define "pgmajorversion 16" -ba ~/rpmbuild/SPECS/pg_search.spec
rpmbuild --without debuginfo --define "pgmajorversion 16" -ba ~/rpmbuild/SPECS/pg_analytics.spec
rpmbuild --without debuginfo --define "pgmajorversion 15" -ba ~/rpmbuild/SPECS/pg_search.spec
rpmbuild --without debuginfo --define "pgmajorversion 15" -ba ~/rpmbuild/SPECS/pg_analytics.spec

from paradedb.

We've just added Debian 11 and 12 packages with release v0.7.3: https://github.com/paradedb/paradedb/releases/tag/v0.7.3

We'll do some more testing for RPM packages, and then we'll add support for those as well soon!

from paradedb.

We've just added Debian 11 and 12 packages with release v0.7.3: https://github.com/paradedb/paradedb/releases/tag/v0.7.3

We'll do some more testing for RPM packages, and then we'll add support for those as well soon!

I have a basic setup for RHEL on https://github.com/paradedb/paradedb/tree/phil/rhel. Will slowly move this along alongside other priorities.

from paradedb.

@Vonng I've got a first version working. Right now it does pg_search for RHEL 9 on Postgres 16 and x86_64. But it'll be very quick to add everything else.

You can find the test release here: https://github.com/paradedb/paradedb/releases/tag/v0.0.0

Could you give it a shot and let me know if it works the way you were expecting?

from paradedb.

I've also added arm64 support: https://github.com/paradedb/paradedb/releases/tag/v0.0.0

from paradedb.

PR up for EL 9. There's a few things missing for EL 8, so that'll come separately

from paradedb.

from paradedb.

Hi Phil, Apologies for the delayed response. I was at PGCon.Dev in Canada and took a trip to Banff, so I'm just catching up on emails now. I've noticed the Deb packages from ParadeDB, and they are fantastic — I really appreciate the effort! I'm puzzled about why the v0.0.0 release does not include RPMs for pg_analytics and pg_lakehouse. Ideally, the RPM offerings would cover combinations of (EL8 / EL9) x (PG 15 / PG 16) x (amd64, arm64/aarch64) x (pg_analytics, pg_lakehouse, pg_search). But it's okay to get started with it. One small suggestion: aligning the RPM naming convention with the PGDG RPM repository would be beneficial. https://download.postgresql.org/pub/repos/yum/16/redhat/rhel-9-x86_64/ For instance: pg_search_16-0.7.0-1PIGSTY.el9.x86_64.rpm pg_lakehouse_16-0.7.0-1PIGSTY.el9.x86_64.rpm pg_analytics_15-0.7.0-1PIGSTY.el9.x86_64.rpm​pg_search_16-0.7.0-1PIGSTY.el8.aarch64.rpm pg_lakehouse_16-0.7.0-1PIGSTY.el8.aarch64.rpm pg_analytics_15-0.7.0-1PIGSTY.el8.aarch64.rpm The example package names are shown above. Append the PG major version with _ , then the extension version string with -, and the release number and repo name with - . and suffixes like el8 or el9 for the RHEL version with . , finally concat with the arch code like x86_64 or aarch64. Additionally, during PGCon.Dev, I spoke with a maintainer of the PGDG RPM repository, who mentioned that extensions written in Rust or Go would never be included in the PGDG RPM repo. While this might be useful info for you, I'm enthusiastic about the prospect of providing Rust extensions in our RPM/APT repository. I'll start testing these RPMs and will keep you updated via email. Cheers, Vonng
…
2024年6月8日 07:02，Philippe Noël @.***> 写道： PR up for EL 9. There's a few things missing for EL 8, so that'll come separately — Reply to this email directly, view it on GitHub https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fparadedb%2Fparadedb%2Fissues%2F1116%23issuecomment-2155674162&data=05%7C02%7C%7C52191fd7553e40b6582308dc8745e717%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638533981507295442%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=uJ0Zk7vbqoW1TA%2Fi1cpX5n2vNkjUilaccokIQY59YQA%3D&reserved=0, or unsubscribe https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACBQRES3P2DRS4BV56UDDZTZGI3YHAVCNFSM6AAAAABHOKDNESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJVGY3TIMJWGI&data=05%7C02%7C%7C52191fd7553e40b6582308dc8745e717%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638533981507307997%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C&sdata=bH2rw%2FplSEp2Ktth8slQ4Hhzy1aQwYbGRw%2FtT%2BRzDDI%3D&reserved=0. You are receiving this because you were mentioned.

the v0.0.0 is only a test to make sure it works, not the full release, which will go in v0.7.6. I'm open to changing the naming convention but I wanted to keep it the same as for our other .deb

from paradedb.

Yeah the debian apt package name works (beware of the - and _ in deb names).
Since rpm is newly introduced, they could adopt a different but consistent naming pattern. ;)

the v0.0.0 is only a test to make sure it works, not the full release, which will go in v0.7.6. I'm open to changing the naming convention but I wanted to keep it the same as for our other .deb

from paradedb.