Thread: postgis for beta releases
Would you consider building packages during beta ? This would allow us to do testing more easily, and I'm guessing that's true for other people too, which leads to wider field testing.
+1 > On Jul 10, 2020, at 1:04 PM, Justin Pryzby <pryzby@telsasoft.com> wrote: > > Would you consider building packages during beta ? > > This would allow us to do testing more easily, and I'm guessing that's true for > other people too, which leads to wider field testing. > >
Hi, On Fri, 2020-07-10 at 15:04 -0500, Justin Pryzby wrote: > Would you consider building packages during beta ? You mean PostGIS 3.1? I thought I pushed it already :( Built packages now. They will sync soon to v13 testing repos. Would you like me to build against v12 as well? Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
On Sat, Jul 11, 2020 at 05:09:12PM +0100, Devrim Gündüz wrote: > On Fri, 2020-07-10 at 15:04 -0500, Justin Pryzby wrote: > > Would you consider building packages during beta ? > > You mean PostGIS 3.1? I thought I pushed it already :( I think the postgis that exists for the stable release(12) should also be built for the beta release(13). That allows test upgrades by 1) installing same postgis for new postgres; and 2) pg_upgrade. Whether to build a new version of postgis is a separate question, but if you do, I'd suggest to build for both versions of postgres when possible. That allows choice of which to upgrade first. During beta period in previous years, postgis has been the one important thing missing. That requires us to drop our postgis columns for beta testing. Last year for the first time, I instead built postgis locally on a couple servers. I think most packages aren't built for beta, which is no problem (although I think they sometimes needed to be added after the fact). These are on our list: pg_repack, fincore, libpqxx-devel. -- Justin
On Sat, Jul 11, 2020 at 05:09:12PM +0100, Devrim Gündüz wrote: > > Hi, > > On Fri, 2020-07-10 at 15:04 -0500, Justin Pryzby wrote: > > Would you consider building packages during beta ? > > You mean PostGIS 3.1? I thought I pushed it already :( > > Built packages now. They will sync soon to v13 testing repos. Would > you like me to build against v12 as well? Thanks - I see that postgis31 is available for postgres13. As I mentioned, I think postgis30 should *also* be built for v13, and postgis31 should *maybe* be built for v12: On Sat, Jul 11, 2020 at 11:46:20AM -0500, Justin Pryzby wrote: > I think the postgis that exists for the stable release(12) should also be built > for the beta release(13). That allows test upgrades by 1) installing same > postgis for new postgres; and 2) pg_upgrade. > > Whether to build a new version of postgis is a separate question, but if you > do, I'd suggest to build for both versions of postgres when possible. That > allows choice of which to upgrade first. > > During beta period in previous years, postgis has been the one important thing > missing. That requires us to drop our postgis columns for beta testing. Last > year for the first time, I instead built postgis locally on a couple servers. > > I think most packages aren't built for beta, which is no problem (although I > think they sometimes needed to be added after the fact). These are on our > list: pg_repack, fincore, libpqxx-devel.
Hi, On Tue, 2020-07-21 at 13:16 -0500, Justin Pryzby wrote: > As I mentioned, I think postgis30 should *also* be built for v13, and > postgis31 > > should *maybe* be built for v12: Pushing them to v11 and v12 *testing* repos in an hour or so. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
On Tue, Jul 28, 2020 at 11:14:43AM +0100, Devrim Gündüz wrote: > On Tue, 2020-07-21 at 13:16 -0500, Justin Pryzby wrote: > > As I mentioned, I think postgis30 should *also* be built for v13, and > > postgis31 should *maybe* be built for v12: > > Pushing them to v11 and v12 *testing* repos in an hour or so. Note, I still suggest that postgis30 and postgis31 should *both* be built for postgres13 and (at least) postgres12. I've done a couple test upgrades from pg12 to 13, some using pg_dump/restore, some using pg_upgrade. In both cases, I first had to do: |DROP AGGREGATE st_union(geometry); |DROP FUNCTION pgis_geometry_union_transfn; I guess postgis30 and 31 are "compatible enough" that I was able to restore a postgis30 DB into a DB with only postgis31 available. Normally, I'd have to do a "rolling upgrade", either: (pg12+gis30) => (pg12+gis31) => (pg13+gis31), or: (pg12+gis30) => (pg13+gis30) => (pg13+gis31). I guess this is related to postgis commit 75a044c61: |Author: Paul Ramsey <pramsey@cleverelephant.ca> |Date: Fri Oct 4 18:25:46 2019 +0000 | Restore ST_Union() aggregate signature and re-work... -- Justin
Hi Justin, On Sat, 2020-09-12 at 16:56 -0500, Justin Pryzby wrote: > Note, I still suggest that postgis30 and postgis31 should *both* be > built for > > postgres13 and (at least) postgres12. :( Looks like you found *the* only package I forgot to move from 12testing to 12 stable repos. Just built it against v12 and v11. Will sync them on Thursday latest, along with PG 13 rc1. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
I'm suggesting to be build postgis31 for pg14. It might be reasonable to wait for beta2, though. Copying last year's correspondence for pg13. On Fri, Jul 10, 2020 at 03:04:30PM -0500, Justin Pryzby wrote: > Would you consider building packages during beta ? > > This would allow us to do testing more easily, and I'm guessing that's true for > other people too, which leads to wider field testing. On Sat, Jul 11, 2020 at 11:46:20AM -0500, Justin Pryzby wrote: > On Sat, Jul 11, 2020 at 05:09:12PM +0100, Devrim Gündüz wrote: > > On Fri, 2020-07-10 at 15:04 -0500, Justin Pryzby wrote: > > > Would you consider building packages during beta ? > > > > You mean PostGIS 3.1? I thought I pushed it already :( > > I think the postgis that exists for the stable release(12) should also be built > for the beta release(13). That allows test upgrades by 1) installing same > postgis for new postgres; and 2) pg_upgrade. > > Whether to build a new version of postgis is a separate question, but if you > do, I'd suggest to build for both versions of postgres when possible. That > allows choice of which to upgrade first. > > During beta period in previous years, postgis has been the one important thing > missing. That requires us to drop our postgis columns for beta testing. Last > year for the first time, I instead built postgis locally on a couple servers. > > I think most packages aren't built for beta, which is no problem (although I > think they sometimes needed to be added after the fact). These are on our > list: pg_repack, fincore, libpqxx-devel. > > -- > Justin On Tue, Jul 21, 2020 at 01:16:39PM -0500, Justin Pryzby wrote: > On Sat, Jul 11, 2020 at 05:09:12PM +0100, Devrim Gündüz wrote: > > > > Hi, > > > > On Fri, 2020-07-10 at 15:04 -0500, Justin Pryzby wrote: > > > Would you consider building packages during beta ? > > > > You mean PostGIS 3.1? I thought I pushed it already :( > > > > Built packages now. They will sync soon to v13 testing repos. Would > > you like me to build against v12 as well? > > Thanks - I see that postgis31 is available for postgres13. > > As I mentioned, I think postgis30 should *also* be built for v13, and postgis31 > should *maybe* be built for v12: > > On Sat, Jul 11, 2020 at 11:46:20AM -0500, Justin Pryzby wrote: > > I think the postgis that exists for the stable release(12) should also be built > > for the beta release(13). That allows test upgrades by 1) installing same > > postgis for new postgres; and 2) pg_upgrade. > > > > Whether to build a new version of postgis is a separate question, but if you > > do, I'd suggest to build for both versions of postgres when possible. That > > allows choice of which to upgrade first. > > > > During beta period in previous years, postgis has been the one important thing > > missing. That requires us to drop our postgis columns for beta testing. Last > > year for the first time, I instead built postgis locally on a couple servers. > > > > I think most packages aren't built for beta, which is no problem (although I > > think they sometimes needed to be added after the fact). These are on our > > list: pg_repack, fincore, libpqxx-devel. On Sat, Sep 12, 2020 at 04:56:06PM -0500, Justin Pryzby wrote: > On Tue, Jul 28, 2020 at 11:14:43AM +0100, Devrim Gündüz wrote: > > On Tue, 2020-07-21 at 13:16 -0500, Justin Pryzby wrote: > > > As I mentioned, I think postgis30 should *also* be built for v13, and > > > postgis31 should *maybe* be built for v12: > > > > Pushing them to v11 and v12 *testing* repos in an hour or so. > > Note, I still suggest that postgis30 and postgis31 should *both* be built for > postgres13 and (at least) postgres12. > > I've done a couple test upgrades from pg12 to 13, some using pg_dump/restore, > some using pg_upgrade. In both cases, I first had to do: > > |DROP AGGREGATE st_union(geometry); > |DROP FUNCTION pgis_geometry_union_transfn; > > I guess postgis30 and 31 are "compatible enough" that I was able to restore a > postgis30 DB into a DB with only postgis31 available. > > Normally, I'd have to do a "rolling upgrade", either: > (pg12+gis30) => (pg12+gis31) => (pg13+gis31), or: > (pg12+gis30) => (pg13+gis30) => (pg13+gis31). > > I guess this is related to postgis commit 75a044c61: > > |Author: Paul Ramsey <pramsey@cleverelephant.ca> > |Date: Fri Oct 4 18:25:46 2019 +0000 > | Restore ST_Union() aggregate signature and re-work...
Re: Justin Pryzby > I'm suggesting to be build postgis31 for pg14. > It might be reasonable to wait for beta2, though. I tried for Debian, and it fails: postgis 3.1.1+dfsg-1.pgdg+2 (amd64) 22:58:44 gserialized_supportfn.c:420:11: error: too few arguments to function ‘is_pseudo_constant_for_index’ 22:58:44 420 | if (!is_pseudo_constant_for_index((Node*)expandexpr, req->index)) 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ 22:58:44 In file included from gserialized_supportfn.c:38: 22:58:44 /usr/include/postgresql/14/server/optimizer/optimizer.h:100:13: note: declared here 22:58:44 100 | extern bool is_pseudo_constant_for_index(PlannerInfo *root, Node *expr, 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ Christoph
Re: To Justin Pryzby > I tried for Debian, and it fails: > > postgis 3.1.1+dfsg-1.pgdg+2 (amd64) > > 22:58:44 gserialized_supportfn.c:420:11: error: too few arguments to function ‘is_pseudo_constant_for_index’ > 22:58:44 420 | if (!is_pseudo_constant_for_index((Node*)expandexpr, req->index)) > 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ > 22:58:44 In file included from gserialized_supportfn.c:38: > 22:58:44 /usr/include/postgresql/14/server/optimizer/optimizer.h:100:13: note: declared here > 22:58:44 100 | extern bool is_pseudo_constant_for_index(PlannerInfo *root, Node *expr, > 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ Full build log: https://pgdgbuild.dus.dg-i.net/view/Binaries-Beta/job/postgis-binaries-beta/lastFailedBuild/architecture=amd64,distribution=sid/consoleFull Christoph
3.1.1 wouldn't have pg14 support yet. master branch does, and I'll backport pg14 into 3.1 branch P > On May 20, 2021, at 12:36 PM, Christoph Berg <myon@debian.org> wrote: > > Re: To Justin Pryzby >> I tried for Debian, and it fails: >> >> postgis 3.1.1+dfsg-1.pgdg+2 (amd64) >> >> 22:58:44 gserialized_supportfn.c:420:11: error: too few arguments to function ‘is_pseudo_constant_for_index’ >> 22:58:44 420 | if (!is_pseudo_constant_for_index((Node*)expandexpr, req->index)) >> 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> 22:58:44 In file included from gserialized_supportfn.c:38: >> 22:58:44 /usr/include/postgresql/14/server/optimizer/optimizer.h:100:13: note: declared here >> 22:58:44 100 | extern bool is_pseudo_constant_for_index(PlannerInfo *root, Node *expr, >> 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Full build log: https://pgdgbuild.dus.dg-i.net/view/Binaries-Beta/job/postgis-binaries-beta/lastFailedBuild/architecture=amd64,distribution=sid/consoleFull > > Christoph
On Thu, May 20, 2021 at 12:52:25PM -0700, Paul Ramsey wrote: > 3.1.1 wouldn't have pg14 support yet. master branch does, and I'll backport pg14 into 3.1 branch I see it's available since May 21. Devrim, would you want to build for v14 ? On May 20, 2021, at 12:36 PM, Christoph Berg <myon@debian.org> wrote: > Re: To Justin Pryzby >> I tried for Debian, and it fails: >> >> postgis 3.1.1+dfsg-1.pgdg+2 (amd64) >> >> 22:58:44 gserialized_supportfn.c:420:11: error: too few arguments to function ‘is_pseudo_constant_for_index’ >> 22:58:44 420 | if (!is_pseudo_constant_for_index((Node*)expandexpr, req->index)) >> 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> 22:58:44 In file included from gserialized_supportfn.c:38: >> 22:58:44 /usr/include/postgresql/14/server/optimizer/optimizer.h:100:13: note: declared here >> 22:58:44 100 | extern bool is_pseudo_constant_for_index(PlannerInfo *root, Node *expr, >> 22:58:44 | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > Full build log: https://pgdgbuild.dus.dg-i.net/view/Binaries-Beta/job/postgis-binaries-beta/lastFailedBuild/architecture=amd64,distribution=sid/consoleFull
Hi, On Tue, 2021-06-01 at 18:39 -0500, Justin Pryzby wrote: > I see it's available since May 21. > Devrim, would you want to build for v14 ? I'm trying to collect a list of packages that can or cannot be compiled against v14. Once that is complete, I will kick an initial set of builds. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
On Wed, Jun 02, 2021 at 09:41:41AM +0100, Devrim Gündüz wrote: > On Tue, 2021-06-01 at 18:39 -0500, Justin Pryzby wrote: > > I see it's available since May 21. > > Devrim, would you want to build for v14 ? > > I'm trying to collect a list of packages that can or cannot be compiled > against v14. Once that is complete, I will kick an initial set of > builds. Would you consider building postgis for pg14b3 ? Thanks, -- Justin
Hi, On Mon, 2021-08-16 at 17:38 -0500, Justin Pryzby wrote: > On Wed, Jun 02, 2021 at 09:41:41AM +0100, Devrim Gündüz wrote: > > On Tue, 2021-06-01 at 18:39 -0500, Justin Pryzby wrote: > > > I see it's available since May 21. > > > Devrim, would you want to build for v14 ? > > > > I'm trying to collect a list of packages that can or cannot be > > compiled > > against v14. Once that is complete, I will kick an initial set of > > builds. > > Would you consider building postgis for pg14b3 ? Done. Syncing to repos. Cheers, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
Hi Justin, On Mon, 2021-08-16 at 17:38 -0500, Justin Pryzby wrote: > Would you consider building postgis for pg14b3 ? In addition to 3.1.x, 3.2.0 alpha1 RPMs will be ready in an hour. Please enable v14testing repo for these packages. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
On Thu, Aug 26, 2021 at 04:05:21PM +0100, Devrim Gündüz wrote: > On Mon, 2021-08-16 at 17:38 -0500, Justin Pryzby wrote: > > On Wed, Jun 02, 2021 at 09:41:41AM +0100, Devrim Gündüz wrote: > > > On Tue, 2021-06-01 at 18:39 -0500, Justin Pryzby wrote: > > > > I see it's available since May 21. > > > > Devrim, would you want to build for v14 ? > > > > > > I'm trying to collect a list of packages that can or cannot be > > > compiled > > > against v14. Once that is complete, I will kick an initial set of > > > builds. > > > > Would you consider building postgis for pg14b3 ? > > Done. Syncing to repos. I'm not sure if it's too early to ask, but would you consider building postgis for pg15b1 ? Also, could you build v15 with --enable-zstd ? Also, it looks like there's no entry in the yum repo file for pgdg15-updates-testing-debuginfo. Thanks, -- Justin
> I'm not sure if it's too early to ask, but would you consider building postgis for > pg15b1 ? > > Also, could you build v15 with --enable-zstd ? > > Also, it looks like there's no entry in the yum repo file for pgdg15-updates- > testing-debuginfo. > > Thanks, > -- > Justin > Devrim and Christian if you need a tagged PostGIS package, I can push out a PostGIS 3.3.0alpha1 release after I get PostGIS PSC agreement on it. PostGIS 3.2 will not work with PostgreSQL 15. Thanks, Regina
Re: Regina Obe
> Devrim and Christian if you need a tagged PostGIS package, I can push out
> a PostGIS 3.3.0alpha1 release after I get PostGIS PSC agreement on it.
> PostGIS 3.2 will not work with PostgreSQL 15.
Yes that would be helpful.
The current version fails with
lwgeom_out_geojson.c:38:9: error: redeclaration of enumerator ‘JSONTYPE_NULL’
38 | JSONTYPE_NULL, /* null, so we didn't bother to identify */
| ^~~~~~~~~~~~~
In file included from lwgeom_out_geojson.c:21:
/usr/include/postgresql/15/server/utils/json.h:21:9: note: previous definition of ‘JSONTYPE_NULL’ with type ‘enum
<anonymous>’
21 | JSONTYPE_NULL, /* null, so we didn't bother to identify */
| ^~~~~~~~~~~~~
Christoph
Hi,
On Thu, 2022-05-19 at 11:16 -0500, Justin Pryzby wrote:
>
> Also, could you build v15 with --enable-zstd ?
commit 1bd03ce822dea86438ae538bdbd39600359c0133
Author: Devrim Gündüz <devrim@gunduz.org>
Date: Thu Mar 31 12:19:30 2022 +0100
--
PostgreSQL 15: Compile with --with-zstd to support zstd compression
of full-page writes in WAL
Regards,
--
Devrim Gündüz
Open Source Solution Architect, Red Hat Certified Engineer
Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
Hmm I think this is being evaluated as "0" for rhel, so needs to test for suse_version > 0. https://git.postgresql.org/gitweb/?p=pgrpms.git;a=blob;f=rpm/redhat/main/non-common/postgresql-15/main/postgresql-15.spec;h=7da2dbc72f1cdee8003c7d71b6ccead89adc85ce;hb=3a5d4584b9c18de8c42d172032c01bfe948c8167 640 %if 0%{?suse_version} <= 1315 641 %else 642 --with-zstd \ 643 %endif postgresql15-15.0-beta1_PGDG.rhel7.x86_64 ts=# SELECT version(), setting FROM pg_config() WHERE name='CONFIGURE'; version|PostgreSQL 15beta1 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-44), 64-bit setting| '--enable-rpath' '--prefix=/usr/pgsql-15' '--includedir=/usr/pgsql-15/include' '--mandir=/usr/pgsql-15/share/man''--datadir=/usr/pgsql-15/share' '--libdir=/usr/pgsql-15/lib' '--with-lz4' '--enable-debug''--enable-cassert' '--with-icu' '--with-llvm' '--with-perl' '--with-python' '--with-tcl' '--with-tclconfig=/usr/lib64''--with-openssl' '--with-pam' '--with-gssapi' '--with-includes=/usr/include' '--with-libraries=/usr/lib64''--enable-nls' '--enable-dtrace' '--with-uuid=e2fs' '--with-libxml' '--with-libxslt' '--with-ldap''--with-selinux' '--with-systemd' '--with-system-tzdata=/usr/share/zoneinfo' '--sysconfdir=/etc/sysconfig/pgsql''--docdir=/usr/pgsql-15/doc' '--htmldir=/usr/pgsql-15/doc/html' 'CFLAGS=-O2 -g -pipe -Wall-Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64-mtune=generic' 'LLVM_CONFIG=/usr/lib64/llvm5.0/bin/llvm-config' 'CLANG=/opt/rh/llvm-toolset-7/root/usr/bin/clang' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig''PYTHON=/usr/bin/python3' postgres=# SET wal_compression =zstd; ERROR: invalid value for parameter "wal_compression": "zstd" HINT: Available values: pglz, lz4, on, off. [pryzbyj@template0 ~]$ sudo rpm -e libzstd-1.5.2-1.el7.x86_64 error: Failed dependencies: libzstd >= 1.4.0 is needed by (installed) postgresql15-15.0-beta1_PGDG.rhel7.x86_64 On Mon, May 23, 2022 at 09:11:00PM +0100, Devrim Gündüz wrote: > Hi, > > On Thu, 2022-05-19 at 11:16 -0500, Justin Pryzby wrote: > > > > Also, could you build v15 with --enable-zstd ? > > commit 1bd03ce822dea86438ae538bdbd39600359c0133 > Author: Devrim Gündüz <devrim@gunduz.org> > Date: Thu Mar 31 12:19:30 2022 +0100 > -- > PostgreSQL 15: Compile with --with-zstd to support zstd compression > of full-page writes in WAL -- Justin Pryzby System Administrator Telsasoft +1-952-707-8581
Hi Justin, On Mon, 2022-05-23 at 15:42 -0500, Justin Pryzby wrote: > think this is being evaluated as "0" for rhel, so needs to test for > suse_version > 0. > > https://git.postgresql.org/gitweb/?p=pgrpms.git;a=blob;f=rpm/redhat/main/non-common/postgresql-15/main/postgresql-15.spec;h=7da2dbc72f1cdee8003c7d71b6ccead89adc85ce;hb=3a5d4584b9c18de8c42d172032c01bfe948c8167 > 640 %if 0%{?suse_version} <= 1315 > 641 %else > 642 --with-zstd \ > 643 %endif <snip> Oops... Fixed. Thanks for the report. beta1_2 packages are now syncing to mirrors, they will be available in a couple of minutes or so. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > I'm not sure if it's too early to ask, but would you consider building postgis > for pg15b1 ? On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > Also, it looks like there's no entry in the yum repo file for > pgdg15-updates-testing-debuginfo. Checking back about these parts. -- Justin
Hi Justin, On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote: > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > I'm not sure if it's too early to ask, but would you consider > > building postgis > > for pg15b1 ? > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > Also, it looks like there's no entry in the yum repo file for > > pgdg15-updates-testing-debuginfo. > > Checking back about these parts. > Done. I had issues building 3.3 with Proj 9.0, so switched back to 8.2. Also wanted to push GeOS 3.11.0 first. Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as well. Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing repository. There is a problem with gdal34 packaging on RHEL 7, and I'll push RHEL 7 packages as soon as I (hopefully can) resolve it. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
Devrim, FYI I'm in the middle of packaging PostGIS 3.3.0beta2. So I should be done with that today. I would like to know what kind of issues you are having building with Proj 9.0. One of our CI bots does build with Proj 9.0/ PG15, but that's a debian bot https://github.com/postgis/postgis/runs/7328183892?check_suite_focus=true I'm hoping to have some CI coverage for yum / CentOS in the coming months so we can catch any of these issues early. At anyrate, no new features are enabled with Proj 9.0 on the PostGIS front so building with Proj 8+ is fine. Main new featuresrequire GEOS 3.11. Thanks, Regina > -----Original Message----- > From: Devrim Gündüz [mailto:devrim@gunduz.org] > Sent: Wednesday, July 13, 2022 10:09 AM > To: Justin Pryzby <pryzby@telsasoft.com> > Cc: Paul Ramsey <pramsey@cleverelephant.ca>; Christoph Berg > <myon@debian.org>; pgsql-pkg-yum@postgresql.org > Subject: Re: postgis for beta releases > > Hi Justin, > > On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote: > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > I'm not sure if it's too early to ask, but would you consider > > > building postgis for pg15b1 ? > > > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > Also, it looks like there's no entry in the yum repo file for > > > pgdg15-updates-testing-debuginfo. > > > > Checking back about these parts. > > > Done. > > I had issues building 3.3 with Proj 9.0, so switched back to 8.2. Also wanted > to push GeOS 3.11.0 first. > > Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as well. > > Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing repository. > There is a problem with gdal34 packaging on RHEL 7, and I'll push RHEL 7 > packages as soon as I (hopefully can) resolve it. > > Regards, > > -- > Devrim Gündüz > Open Source Solution Architect, Red Hat Certified Engineer > Twitter: @DevrimGunduz , @DevrimGunduzTR
FYI released: https://postgis.net/2022/07/13/postgis-3.3.0beta2/ Thanks, Regina > -----Original Message----- > From: Regina Obe [mailto:lr@pcorp.us] > Sent: Wednesday, July 13, 2022 4:26 PM > To: 'Devrim Gündüz' <devrim@gunduz.org>; 'Justin Pryzby' > <pryzby@telsasoft.com> > Cc: 'Paul Ramsey' <pramsey@cleverelephant.ca>; 'Christoph Berg' > <myon@debian.org>; 'pgsql-pkg-yum@postgresql.org' <pgsql-pkg- > yum@postgresql.org> > Subject: RE: postgis for beta releases > > Devrim, > > FYI I'm in the middle of packaging PostGIS 3.3.0beta2. > So I should be done with that today. > > I would like to know what kind of issues you are having building with Proj 9.0. > One of our CI bots does build with Proj 9.0/ PG15, but that's a debian bot > https://github.com/postgis/postgis/runs/7328183892?check_suite_focus=tru > e > > I'm hoping to have some CI coverage for yum / CentOS in the coming months > so we can catch any of these issues early. > > At anyrate, no new features are enabled with Proj 9.0 on the PostGIS front so > building with Proj 8+ is fine. Main new features require GEOS 3.11. > > Thanks, > Regina > > > > -----Original Message----- > > From: Devrim Gündüz [mailto:devrim@gunduz.org] > > Sent: Wednesday, July 13, 2022 10:09 AM > > To: Justin Pryzby <pryzby@telsasoft.com> > > Cc: Paul Ramsey <pramsey@cleverelephant.ca>; Christoph Berg > > <myon@debian.org>; pgsql-pkg-yum@postgresql.org > > Subject: Re: postgis for beta releases > > > > Hi Justin, > > > > On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote: > > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > > I'm not sure if it's too early to ask, but would you consider > > > > building postgis for pg15b1 ? > > > > > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > > Also, it looks like there's no entry in the yum repo file for > > > > pgdg15-updates-testing-debuginfo. > > > > > > Checking back about these parts. > > > > > Done. > > > > I had issues building 3.3 with Proj 9.0, so switched back to 8.2. > > Also wanted to push GeOS 3.11.0 first. > > > > Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as well. > > > > Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing repository. > > There is a problem with gdal34 packaging on RHEL 7, and I'll push RHEL > > 7 packages as soon as I (hopefully can) resolve it. > > > > Regards, > > > > -- > > Devrim Gündüz > > Open Source Solution Architect, Red Hat Certified Engineer > > Twitter: @DevrimGunduz , @DevrimGunduzTR
On Wed, Jul 13, 2022 at 03:09:02PM +0100, Devrim Gündüz wrote: > Hi Justin, > > On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote: > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > I'm not sure if it's too early to ask, but would you consider > > > building postgis > > > for pg15b1 ? > > > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > Also, it looks like there's no entry in the yum repo file for > > > pgdg15-updates-testing-debuginfo. > > > > Checking back about these parts. > > Done. Thanks. Few things: I don't know if the updated repo package with debuginfo is pushed (for rh7). I just had to manually add the pg15 debuginfo repo. Also, I think the beta packages should be built with -Og rather than -O2. cassert will make it slower than debug would make it faster anyway. Also, I think that postgis32 should be built for pg15. This allows installing the same package for both old and new postgres versions before doing pg_upgrade. > I had issues building 3.3 with Proj 9.0, so switched back to 8.2. Also > wanted to push GeOS 3.11.0 first. > > Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as > well. > > Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing > repository. There is a problem with gdal34 packaging on RHEL 7, and > I'll push RHEL 7 packages as soon as I (hopefully can) resolve it. -- Justin
> Also, I think that postgis32 should be built for pg15. This allows installing the > same package for both old and new postgres versions before doing > pg_upgrade. This is not needed anymore since PostGIS 3, since the lib file no longer has the minor. So doing pg_upgrade from PostgreSQL x 3.2 straight to PostgreSQL 15 3.3.0 will work just fine. For regression testing, it's useful. We are planning to release PostGIS 3.3.0 before the end of this month. Thanks, Regina
Hi Regina, On Wed, 2022-07-13 at 16:25 -0400, Regina Obe wrote: > I would like to know what kind of issues you are having building with > Proj 9.0. Sorry for the late reply. I fixed it a couple of days ago: It was a spec file issue. Thanks! Cheers, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
Hi, On Thu, 2022-08-18 at 08:38 -0500, Justin Pryzby wrote: > I don't know if the updated repo package with debuginfo is pushed > (for rh7). I just had to manually add the pg15 debuginfo repo. Oops. Great catch. Fix committed: https://git.postgresql.org/gitweb/?p=pgrpms.git;a=commit;h=2a702c50c5e5ec21fc48daff2d227e17280e38e9 (Also fixed Fedora repo RPM as well). I'll release new set of repo rpms along with some new packages later today. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
Hi Justin, On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote: > > Also, it looks like there's no entry in the yum repo file for > > pgdg15-updates-testing-debuginfo. > > Checking back about these parts. Added this a couple of weeks ago. Thanks again for heads up. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
Hi Devrim Thanks for packaging pg15 ! Do you know when postgis will be available ? It's still only in the "testing" repo, and I think wouldn't have compiled since beta4. -- Justin Pryzby System Administrator Telsasoft +1-952-707-8581 On Wed, Jul 13, 2022 at 03:09:02PM +0100, Devrim Gündüz wrote: > Hi Justin, > > On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote: > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > I'm not sure if it's too early to ask, but would you consider > > > building postgis > > > for pg15b1 ? > > > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > Also, it looks like there's no entry in the yum repo file for > > > pgdg15-updates-testing-debuginfo. > > > > Checking back about these parts. > > > Done. > > I had issues building 3.3 with Proj 9.0, so switched back to 8.2. Also > wanted to push GeOS 3.11.0 first. > > Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as > well. > > Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing > repository. There is a problem with gdal34 packaging on RHEL 7, and > I'll push RHEL 7 packages as soon as I (hopefully can) resolve it.
Hi!
They seem to be in the https://download.postgresql.org/pub/repos/yum/15/ directory already.
Best regards, Matti Linnanvuori
Matti Linnanvuori
Support Engineer
 |
| PORTALIFY Upseerinkatu 1 FI-02600 Espoo | Finland portalify.com | Phone +358 9 6227 9668 matti.linnanvuori@portalify.com |
This information and any attachments are confidential and may solely be for the use of the intended recipient or entity whose address is listed above. If you have received this e-mail by error please notify the sender immediately and delete this message and any attachment from your system. Note that copying, retaining copies or distribution is prohibited and may be unlawful.
From: Justin Pryzby <pryzby@telsasoft.com>
Date: Thursday, 13. October 2022 at 19.56
To: Devrim Gündüz <devrim@gunduz.org>
Cc: Paul Ramsey <pramsey@cleverelephant.ca>, Christoph Berg <myon@debian.org>, pgsql-pkg-yum@postgresql.org <pgsql-pkg-yum@postgresql.org>
Subject: Re: postgis for beta releases
Hi Devrim
Thanks for packaging pg15 !
Do you know when postgis will be available ? It's still only in the
"testing" repo, and I think wouldn't have compiled since beta4.
--
Justin Pryzby
System Administrator
Telsasoft
+1-952-707-8581
On Wed, Jul 13, 2022 at 03:09:02PM +0100, Devrim Gündüz wrote:
> Hi Justin,
>
> On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote:
> > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote:
> > > I'm not sure if it's too early to ask, but would you consider
> > > building postgis
> > > for pg15b1 ?
> >
> > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote:
> > > Also, it looks like there's no entry in the yum repo file for
> > > pgdg15-updates-testing-debuginfo.
> >
> > Checking back about these parts.
> >
> Done.
>
> I had issues building 3.3 with Proj 9.0, so switched back to 8.2. Also
> wanted to push GeOS 3.11.0 first.
>
> Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as
> well.
>
> Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing
> repository. There is a problem with gdal34 packaging on RHEL 7, and
> I'll push RHEL 7 packages as soon as I (hopefully can) resolve it.
Attachment
I see them there for fedora and for RH8 and RH9, but not yet for RH7. https://download.postgresql.org/pub/repos/yum/15/redhat/rhel-7-x86_64/ On Thu, Oct 13, 2022 at 05:40:16PM +0000, Matti Linnanvuori wrote: > Hi! > > They seem to be in the https://download.postgresql.org/pub/repos/yum/15/ directory already. > > Best regards, Matti Linnanvuori > > From: Justin Pryzby <pryzby@telsasoft.com> > Date: Thursday, 13. October 2022 at 19.56 > To: Devrim Gündüz <devrim@gunduz.org> > Cc: Paul Ramsey <pramsey@cleverelephant.ca>, Christoph Berg <myon@debian.org>, pgsql-pkg-yum@postgresql.org <pgsql-pkg-yum@postgresql.org> > Subject: Re: postgis for beta releases > Hi Devrim > > Thanks for packaging pg15 ! > > Do you know when postgis will be available ? It's still only in the > "testing" repo, and I think wouldn't have compiled since beta4. > > -- > Justin Pryzby > System Administrator > Telsasoft > +1-952-707-8581 > > On Wed, Jul 13, 2022 at 03:09:02PM +0100, Devrim Gündüz wrote: > > Hi Justin, > > > > On Mon, 2022-07-11 at 12:47 -0500, Justin Pryzby wrote: > > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > > I'm not sure if it's too early to ask, but would you consider > > > > building postgis > > > > for pg15b1 ? > > > > > > On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > > > > Also, it looks like there's no entry in the yum repo file for > > > > pgdg15-updates-testing-debuginfo. > > > > > > Checking back about these parts. > > > > > Done. > > > > I had issues building 3.3 with Proj 9.0, so switched back to 8.2. Also > > wanted to push GeOS 3.11.0 first. > > > > Meanwhile, I used this opportunity to complete GIS stack for RHEL 9 as > > well. > > > > Pushed packages for RHEL 8, 9 and Fedora, to the v15 testing > > repository. There is a problem with gdal34 packaging on RHEL 7, and > > I'll push RHEL 7 packages as soon as I (hopefully can) resolve it. -- Justin Pryzby System Administrator Telsasoft +1-952-707-8581
Hi Justin, On Thu, 2022-10-13 at 11:55 -0500, Justin Pryzby wrote: > Thanks for packaging pg15 ! You are welcome! > > Do you know when postgis will be available ? It's still only in the > "testing" repo, and I think wouldn't have compiled since beta4. Thanks for heads up. Pushed RHEL 7 packages a couple of hours ago. Needed to make a small change in the spec file. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
On Fri, Oct 14, 2022 at 01:40:22PM +0100, Devrim Gündüz wrote: > Hi Justin, > > On Thu, 2022-10-13 at 11:55 -0500, Justin Pryzby wrote: > > Thanks for packaging pg15 ! > > You are welcome! > > > > Do you know when postgis will be available ? It's still only in the > > "testing" repo, and I think wouldn't have compiled since beta4. > > Thanks for heads up. Pushed RHEL 7 packages a couple of hours ago. > Needed to make a small change in the spec file. Thanks. I think the v15 *.repo file is missing debuginfo, at least for RH7. See also pgrpms commit 2a702c50c from August. -- Justin
Hi, On Fri, 2022-10-14 at 14:53 -0500, Justin Pryzby wrote: > I think the v15 *.repo file is missing debuginfo, at least for > RH7. See also pgrpms commit 2a702c50c from August. Thanks for the report. Fixed in git. Will push new RPMs early next week. Regards, -- Devrim Gündüz Open Source Solution Architect, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR
Attachment
On Thu, May 19, 2022 at 11:16:01AM -0500, Justin Pryzby wrote: > On Thu, Aug 26, 2021 at 04:05:21PM +0100, Devrim Gündüz wrote: > > On Mon, 2021-08-16 at 17:38 -0500, Justin Pryzby wrote: > > > On Wed, Jun 02, 2021 at 09:41:41AM +0100, Devrim Gündüz wrote: > > > > On Tue, 2021-06-01 at 18:39 -0500, Justin Pryzby wrote: > > > > > I see it's available since May 21. > > > > > Devrim, would you want to build for v14 ? > > > > > > > > I'm trying to collect a list of packages that can or cannot be compiled > > > > against v14. Once that is complete, I will kick an initial set of builds. > > > > > > Would you consider building postgis for pg14b3 ? > > > > Done. Syncing to repos. > > I'm not sure if it's too early to ask, but would you consider building postgis > for pg15b1 ? If it's not already on your list, would you consider building postgis for pg16? Thanks, -- Justin
> > > > > > > > Would you consider building postgis for pg14b3 ? > > > > > > Done. Syncing to repos. > > > > I'm not sure if it's too early to ask, but would you consider building > > postgis for pg15b1 ? > > If it's not already on your list, would you consider building postgis for pg16? > > Thanks, > -- > Justin > Devrim. We just released PostGIS 3.4.0beta1 tested against PG16. Much appreciated if you can package that. Other spatial extensions that should be ready to go too pgRouting -- 3.5 (3.6 hasn't hit beta yet, but both should work with PostgreSQL 16) Paul, Hint hint, can you please push a release of ogr_fdw. AS I recall you haven't released since we patched up for PG16 https://github.com/pramsey/pgsql-ogr-fdw/pull/250 Thanks, Regina
On Jul 18, 2023, at 9:50 AM, Regina Obe <lr@pcorp.us> wrote:
Hint hint, can you please push a release of ogr_fdw. AS I recall you
haven't released since we patched up for PG16
https://github.com/pramsey/pgsql-ogr-fdw/pull/250
Tagged and pubbed
P
Hi Justin, On Tue, 2023-07-18 at 08:35 -0500, Justin Pryzby wrote: > If it's not already on your list, would you consider building postgis > for pg16? Already started working on it. Have a small issue, will report upstream. Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR
Hi, On Tue, 2023-07-18 at 08:35 -0500, Justin Pryzby wrote: > If it's not already on your list, would you consider building postgis > for pg16? Committed initial spec file. Will build packages soon. Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR
Hi, On Tue, 2023-07-18 at 09:59 -0700, Paul Ramsey wrote: > https://github.com/pramsey/pgsql-ogr-fdw/releases/tag/v1.1.4 > > Tagged and pubbed Committed spec files. Will release packages soon. Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR
> On Tue, 2023-07-18 at 09:59 -0700, Paul Ramsey wrote: > > https://github.com/pramsey/pgsql-ogr-fdw/releases/tag/v1.1.4 > > > > Tagged and pubbed > > Committed spec files. Will release packages soon. > > Regards, > -- > Devrim Gündüz > Open Source Solution Architect, PostgreSQL Major Contributor > Twitter: @DevrimGunduz , @DevrimGunduzTR Much appreciated and sorry for the issues with the PostGIS release. Thanks, Regina
On Wed, Jul 19, 2023 at 02:49:13PM +0100, Devrim Gündüz wrote: > Hi, > > On Tue, 2023-07-18 at 09:59 -0700, Paul Ramsey wrote: > > https://github.com/pramsey/pgsql-ogr-fdw/releases/tag/v1.1.4 > > > > Tagged and pubbed > > Committed spec files. Will release packages soon. Thanks. Could you build for centos7, too ? -- Justin
On Fri, Jul 28, 2023 at 07:47:57AM -0500, Justin Pryzby wrote: > On Wed, Jul 19, 2023 at 02:49:13PM +0100, Devrim Gündüz wrote: > > Hi, > > > > On Tue, 2023-07-18 at 09:59 -0700, Paul Ramsey wrote: > > > https://github.com/pramsey/pgsql-ogr-fdw/releases/tag/v1.1.4 > > > > > > Tagged and pubbed > > > > Committed spec files. Will release packages soon. > > Thanks. Could you build for centos7, too ? Checking back. -- Justin
Hi Justin, On Fri, 2023-07-28 at 07:47 -0500, Justin Pryzby wrote: > Thanks. Could you build for centos7, too ? I'm considering to drop RHEL 7 support for PostgreSQL 16. That is why I did not build it so far. Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR
On Mon, Aug 14, 2023 at 02:34:01PM +0100, Devrim Gündüz wrote: > Hi Justin, > > On Fri, 2023-07-28 at 07:47 -0500, Justin Pryzby wrote: > > Thanks. Could you build for centos7, too ? > > I'm considering to drop RHEL 7 support for PostgreSQL 16. That is why I > did not build it so far. Thanks for the info. That's not unreasonable, but I wish I had known a few months further in advance, allowing more time to either migrate OSes and/or plan how to deploy it ourselves. I'd assumed that when you built beta packages for pg16/c7, you intended to continue building them. -- Justin
Hi, On Mon, 2023-08-14 at 17:55 -0500, Justin Pryzby wrote: > Thanks for the info. That's not unreasonable, but I wish I had known > a few months further in advance, allowing more time to either migrate > OSes and/or plan how to deploy it ourselves. I'd assumed that when > you built beta packages for pg16/c7, you intended to continue building > them. Apologies for the inconvenience. That was indeed the plan, however further issues building 3rd party packages and the complexity in spec files made things harder for us. Consider all dependencies of PostGIS, for example. Please note that since there is a common spec file of PostgreSQL 16, you can always build RPMS via our repo. Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR
On Fri, Oct 14, 2022 at 02:53:22PM -0500, Justin Pryzby wrote: > On Fri, Oct 14, 2022 at 01:40:22PM +0100, Devrim Gündüz wrote: > > Hi Justin, > > > > On Thu, 2022-10-13 at 11:55 -0500, Justin Pryzby wrote: > > > Thanks for packaging pg15 ! > > > > You are welcome! > > > > > > Do you know when postgis will be available ? It's still only in the > > > "testing" repo, and I think wouldn't have compiled since beta4. > > > > Thanks for heads up. Pushed RHEL 7 packages a couple of hours ago. > > Needed to make a small change in the spec file. > > Thanks. I think the v15 *.repo file is missing debuginfo, at least for > RH7. See also pgrpms commit 2a702c50c from August. It looks like pg16 debuginfo is missing from the *.repo file for RH9.
Hi Justin, On Mon, 2023-10-16 at 07:30 -0500, Justin Pryzby wrote: > It looks like pg16 debuginfo is missing from the *.repo file for RH9. Thanks, fixed. Next time can you please either submit a bug report https://redmine.postgresql.org/projects/pgrpms/issues/new or start a new thread? Thanks! Regards, -- Devrim Gündüz Open Source Solution Architect, PostgreSQL Major Contributor Twitter: @DevrimGunduz , @DevrimGunduzTR