From lr at pcorp.us  Mon Feb  2 12:19:04 2026
From: lr at pcorp.us (Regina Obe)
Date: Mon, 2 Feb 2026 15:19:04 -0500
Subject: Motion: PostGIS releases of 3.0, 3.1 EOL this coming weekend and 3.2,
 3.3, 3.4, 3.5, 3.6 week after
Message-ID: <000001dc9481$2dcd6600$89683200$@pcorp.us>

I'd like to do EOL release this coming weekend of 3.0, 3.1 EOL (final
release) and then patch release of the remaining the week after.

+1

If you have issue with that plan let me know.

Thanks,
Regina




From pramsey at cleverelephant.ca  Mon Feb  2 13:01:55 2026
From: pramsey at cleverelephant.ca (Paul Ramsey)
Date: Mon, 2 Feb 2026 13:01:55 -0800
Subject: Motion: PostGIS releases of 3.0, 3.1 EOL this coming weekend and
 3.2, 3.3, 3.4, 3.5, 3.6 week after
In-Reply-To: <000001dc9481$2dcd6600$89683200$@pcorp.us>
References: <000001dc9481$2dcd6600$89683200$@pcorp.us>
Message-ID: <4AD94937-8495-43D1-A2E7-98EFDB802D35@cleverelephant.ca>

+1 from me

> On Feb 2, 2026, at 12:19?PM, Regina Obe <lr at pcorp.us> wrote:
> 
> I'd like to do EOL release this coming weekend of 3.0, 3.1 EOL (final
> release) and then patch release of the remaining the week after.
> 
> +1
> 
> If you have issue with that plan let me know.
> 
> Thanks,
> Regina
> 
> 
> 


From loic.bartoletti at oslandia.com  Mon Feb  2 22:42:43 2026
From: loic.bartoletti at oslandia.com (=?utf-8?B?TG/Dr2M=?= BARTOLETTI)
Date: Tue, 3 Feb 2026 07:42:43 +0100
Subject: Motion: PostGIS releases of 3.0, 3.1 EOL this coming weekend and
 3.2, 3.3, 3.4, 3.5, 3.6 week after
In-Reply-To: <000001dc9481$2dcd6600$89683200$@pcorp.us>
References: <000001dc9481$2dcd6600$89683200$@pcorp.us>
Message-ID: <aYGY0Sxko6NJo6zs@FreeBSD>

OK for me,
Thanks,
Lo?c

On 02/02/2026 15:19, Regina Obe wrote:
>I'd like to do EOL release this coming weekend of 3.0, 3.1 EOL (final
>release) and then patch release of the remaining the week after.
>
>+1
>
>If you have issue with that plan let me know.
>
>Thanks,
>Regina
>
>
>

From strk at kbt.io  Tue Feb  3 01:52:58 2026
From: strk at kbt.io (Sandro Santilli)
Date: Tue, 3 Feb 2026 10:52:58 +0100
Subject: Motion: PostGIS releases of 3.0, 3.1 EOL this coming weekend and
 3.2, 3.3, 3.4, 3.5, 3.6 week after
In-Reply-To: <000001dc9481$2dcd6600$89683200$@pcorp.us>
References: <000001dc9481$2dcd6600$89683200$@pcorp.us>
Message-ID: <aYHFeqmiE6g1A9gL@oli>

On Mon, Feb 02, 2026 at 03:19:04PM -0500, Regina Obe wrote:
> I'd like to do EOL release this coming weekend of 3.0, 3.1 EOL (final
> release) and then patch release of the remaining the week after.

+1 for EOLing 3.0 and 3.1 with final release. Thanks!

--strk;

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <http://lists.osgeo.org/pipermail/postgis-devel/attachments/20260203/63db0836/attachment.sig>

From t.bussmann at gmx.net  Wed Feb  4 02:53:18 2026
From: t.bussmann at gmx.net (Tobias Bussmann)
Date: Wed, 4 Feb 2026 11:53:18 +0100
Subject: Motion: PostGIS releases of 3.0, 3.1 EOL this coming weekend and
 3.2, 3.3, 3.4, 3.5, 3.6 week after
In-Reply-To: <000001dc9481$2dcd6600$89683200$@pcorp.us>
References: <000001dc9481$2dcd6600$89683200$@pcorp.us>
Message-ID: <942ABF72-AA86-4DAF-860A-FEF0DC9011A5@gmx.net>

Dear Regina,

Great, you are about to package the next releases! 

Please note that the quarterly PostgreSQL releases are also due next week. Packagers usually receive the release tarball on Monday for release on Thursday. As someone who packages Postgres.App, which includes PostGIS, it would be great to release Postgres 18.2 with PostGIS 3.6.2 at the same time. Therefore, I would encourage you to release the PostGIS tarballs by Tuesday at the latest. If that is not possible, the next round of PostGIS updates will be included in the next iteration of builds, which will be released by May at the latest.

In general it would be very helpful to have PostGIS (and other extension) releases aligned a week before the PostgreSQL schedule: <https://www.postgresql.org/developer/roadmap/> and <https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items> for beta schedule

Thanks in advance
Tobias



> Am 02.02.2026 um 21:19 schrieb Regina Obe <lr at pcorp.us>:
> 
> I'd like to do EOL release this coming weekend of 3.0, 3.1 EOL (final
> release) and then patch release of the remaining the week after.
> 
> +1
> 
> If you have issue with that plan let me know.
> 
> Thanks,
> Regina
> 
> 
> 
> 


From lr at pcorp.us  Wed Feb  4 07:34:47 2026
From: lr at pcorp.us (Regina Obe)
Date: Wed, 4 Feb 2026 10:34:47 -0500
Subject: Motion: PostGIS releases of 3.0,
 3.1 EOL this coming weekend and 3.2, 3.3, 3.4, 3.5, 3.6 week after
In-Reply-To: <942ABF72-AA86-4DAF-860A-FEF0DC9011A5@gmx.net>
References: <000001dc9481$2dcd6600$89683200$@pcorp.us>
 <942ABF72-AA86-4DAF-860A-FEF0DC9011A5@gmx.net>
Message-ID: <000001dc95eb$cca80990$65f81cb0$@pcorp.us>

> Dear Regina,
> 
> Great, you are about to package the next releases!
> 
> Please note that the quarterly PostgreSQL releases are also due next week.
> Packagers usually receive the release tarball on Monday for release on
> Thursday. As someone who packages Postgres.App, which includes PostGIS, it
> would be great to release Postgres 18.2 with PostGIS 3.6.2 at the same
time.
> Therefore, I would encourage you to release the PostGIS tarballs by
Tuesday at
> the latest. If that is not possible, the next round of PostGIS updates
will be
> included in the next iteration of builds, which will be released by May at
the
> latest.
> 
> In general it would be very helpful to have PostGIS (and other extension)
> releases aligned a week before the PostgreSQL schedule:
> <https://www.postgresql.org/developer/roadmap/> and
> <https://wiki.postgresql.org/wiki/PostgreSQL_19_Open_Items> for beta
> schedule
> 
> Thanks in advance
> Tobias
> 

Yes Paul and I discussed trying to align our release cycle with PostgreSQL.

I think there are some key open items left in the 3.2-3.6 so sadly not sure
we can make it, but will try.


From lr at pcorp.us  Mon Feb  9 18:27:23 2026
From: lr at pcorp.us (Regina Obe)
Date: Mon, 9 Feb 2026 21:27:23 -0500
Subject: PostGIS Patch releases for 3.0 - 3.6
Message-ID: <000001dc9a34$cb2ca5b0$6185f110$@pcorp.us>

The PostGIS development team is pleased to release patch releases for the
3.0 thru 3.6 PostGIS series.

3.6.2, 3.5.5, 3.4.5, 3.3.9, 3.2.9, 3.1.13, and 3.0.12

Note that this is the last patch release for the 3.0 and 3.1 series.

Refer to  https://postgis.net/2026/02/PostGIS-Patch-Releases/  for details.

If you run into any issues with these, please report on the mailing lists or
submit a ticket following these guidelines -
https://postgis.net/development/bug_reporting/

Happy Testing,
PostGIS Development Team 


From t.bussmann at gmx.net  Wed Feb 11 20:45:50 2026
From: t.bussmann at gmx.net (Tobias Bussmann)
Date: Thu, 12 Feb 2026 05:45:50 +0100
Subject: Motion: PostGIS releases of 3.0, 3.1 EOL this coming weekend and
 3.2, 3.3, 3.4, 3.5, 3.6 week after
In-Reply-To: <000001dc95eb$cca80990$65f81cb0$@pcorp.us>
References: <000001dc9481$2dcd6600$89683200$@pcorp.us>
 <942ABF72-AA86-4DAF-860A-FEF0DC9011A5@gmx.net>
 <000001dc95eb$cca80990$65f81cb0$@pcorp.us>
Message-ID: <B241FB15-DBA4-4635-A998-1A1FFD4B832A@gmx.net>

> Am 04.02.2026 um 16:34 schrieb Regina Obe <lr at pcorp.us>:
> 
> Yes Paul and I discussed trying to align our release cycle with PostgreSQL.

Thank you very much for working on this! This week's releases were right on time.

I found one little issue in the announcement <https://postgis.net/2026/02/PostGIS-Patch-Releases/>: The NEWS file of 3.6.2 miss-linked to the one for 3.5.5

And, unfortunately, a bigger issue with a late patch on the 3.2 and 3.3 branch: <https://trac.osgeo.org/postgis/ticket/5998#comment:15> I will likely have to skip packaging 3.2.9 and 3.3.9 in Postgres.App till this is settled.

Best regards
Tobias


From pryzby at telsasoft.com  Thu Feb 12 06:10:33 2026
From: pryzby at telsasoft.com (Justin Pryzby)
Date: Thu, 12 Feb 2026 08:10:33 -0600
Subject: ERROR:  Could not add geog_brin_inclusion_merge to
 brin_geography_inclusion_ops..null value in column "refobjid" (Re: Do you
 use PostGIS BRIN?)
In-Reply-To: <003c01db8bc5$e79c9b20$b6d5d160$@pcorp.us>
References: <CAG29aDs6kiN1J6-s=3ZPA+NYdRVYJ0JpUmkPjjSdjCL+Bf6q5Q@mail.gmail.com>
 <006501db6089$c7e1c650$57a552f0$@pcorp.us>
 <8e400fa1-6c2d-4331-ab3d-64741aae8ff2@vondra.me>
 <5C4D43C4-62B7-4C73-817C-40FF8B6EF733@cleverelephant.ca>
 <e3839437-da80-4afa-81d8-3851bb82112d@vondra.me>
 <F9C53B87-E1B3-4391-B30E-90CD5D1FB46F@cleverelephant.ca>
 <Z8SuG0uwwEGjLRzK@pryzbyj2023>
 <002201db8bbd$70d81210$52883630$@pcorp.us>
 <Z8Tal9z539mBY_7B@pryzbyj2023>
 <003c01db8bc5$e79c9b20$b6d5d160$@pcorp.us>
Message-ID: <aY3fWcgRBUH38Wqa@pryzbyj2023>

We hit this again while/after upgrading one of our remaining pg17+postgis3.4
customers to pg18+postgis3.6.

# SELECT postgis_full_version();
postgis_full_version | POSTGIS="3.6.1 f533623" [EXTENSION] PGSQL="170" (procs need upgrade for use with PostgreSQL "180") GEOS="3.11.2-CAPI-1.17.2" PROJ="7.1.1 NETWORK_ENABLED=OFF URL_ENDPOINT=https://cdn.proj.org USER_WRITABLE_DIRECTORY=/var/lib/pgsql/.local/share/proj DATABASE_PATH=/usr/proj71/share/proj/proj.db" LIBXML="2.9.1" LIBJSON="0.11" (core procs from "3.4.2 3.4.2" need upgrade)

$ rpm -qa postgis\*
postgis34_17-3.4.2-4PGDG.el7.x86_64
postgis36_18-3.6.1-1PGDG.el7.x86_64

# SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';
  oid  | opcmethod |            opcname             | opcnamespace | opcowner | opcfamily | opcintype | opcdefault | opckeytype 
-------+-----------+--------------------------------+--------------+----------+-----------+-----------+------------+------------
 21756 |      3580 | brin_geometry_inclusion_ops_2d |         2200 |       10 |     21746 |     27847 | t          |      27830
 21768 |      3580 | brin_geometry_inclusion_ops_3d |         2200 |       10 |     21764 |     27847 | f          |      27859
 21778 |      3580 | brin_geometry_inclusion_ops_4d |         2200 |       10 |     21774 |     27847 | f          |      27859

> Also, the data dir was originally initdb'd under centos (7, and probably earlier
> versions before that), and most recently migrated to debian (with the requisite
> reindex).

This time, the server is still running centos7.  I've built my own RPMs for
pg18 and postgis, since pgdg doesn't provides RPMs for new versions on old
OSes.

Let me know if I can add anything else.


On Sun, Mar 02, 2025 at 05:53:23PM -0500, lr at pcorp.us wrote:
> Justin,
> 
> Thanks.  So it looks like brin was never installed in one version of yours
> and in your second the geography brin was never installed.
> 
> We've had issues over the years with some BRIN installs being missing or
> partly missing because of not catching pg_upgrade changes in PostgreSQL
> version.
> 
> Anyrate I'll try to catch this situation and install BRIN if it is found to
> be missing.
> 
> Thanks,
> Regina
> 
> > -----Original Message-----
> > From: Justin Pryzby <pryzby at telsasoft.com>
> > Sent: Sunday, March 2, 2025 5:24 PM
> > To: lr at pcorp.us
> > Cc: Paul Ramsey <pramsey at cleverelephant.ca>; postgis-devel at lists.osgeo.org
> > Subject: Re: ERROR: Could not add geog_brin_inclusion_merge to
> > brin_geography_inclusion_ops..null value in column "refobjid" (Re: Do you
> use
> > PostGIS BRIN?)
> > 
> > On Sun, Mar 02, 2025 at 04:52:48PM -0500, lr at pcorp.us wrote:
> > > I've ticketed this issue here:
> > > https://trac.osgeo.org/postgis/ticket/5856
> > >
> > > I'm going to try to revise the upgrade script to account for this
> scenario.
> > >
> > > Can you do me a favor, send me the output of this from your problem
> > > database:
> > >
> > > SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';
> > 
> > The DB where we hit the error says:
> > 
> > ts=# SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';
> >   oid  | opcmethod |            opcname             | opcnamespace |
> opcowner |
> > opcfamily | opcintype | opcdefault | opckeytype
> >
> -------+-----------+--------------------------------+--------------+--------
> --+-----------
> > +-----------+------------+------------
> >  17704 |      3580 | brin_geometry_inclusion_ops_2d |         2200 |
> 10 |
> > 17694 |     16419 | t          |      16454
> >  17716 |      3580 | brin_geometry_inclusion_ops_3d |         2200 |
> 10 |
> > 17712 |     16419 | f          |      16458
> >  17726 |      3580 | brin_geometry_inclusion_ops_4d |         2200 |
> 10 |
> > 17722 |     16419 | f          |      16458
> > (3 rows)
> > 
> > And the 2nd instance I mentioned which has no
> > opcname='brin_geography_inclusion_ops' says:
> > 
> > ts=# SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';  oid
> > | opcmethod | opcname | opcnamespace | opcowner | opcfamily | opcintype
> > | opcdefault | opckeytype
> >
> -----+-----------+---------+--------------+----------+-----------+----------
> > (0 rows)

-- 
Justin Pryzby
System Administrator
Telsasoft
+1-952-707-8581

From lr at pcorp.us  Thu Feb 12 06:59:42 2026
From: lr at pcorp.us (Regina Obe)
Date: Thu, 12 Feb 2026 09:59:42 -0500
Subject: Motion: PostGIS releases of 3.0,
 3.1 EOL this coming weekend and 3.2, 3.3, 3.4, 3.5, 3.6 week after
In-Reply-To: <B241FB15-DBA4-4635-A998-1A1FFD4B832A@gmx.net>
References: <000001dc9481$2dcd6600$89683200$@pcorp.us>
 <942ABF72-AA86-4DAF-860A-FEF0DC9011A5@gmx.net>
 <000001dc95eb$cca80990$65f81cb0$@pcorp.us>
 <B241FB15-DBA4-4635-A998-1A1FFD4B832A@gmx.net>
Message-ID: <001401dc9c30$385b8f00$a912ad00$@pcorp.us>

> > Am 04.02.2026 um 16:34 schrieb Regina Obe <lr at pcorp.us>:
> >
> > Yes Paul and I discussed trying to align our release cycle with
PostgreSQL.
> 
> Thank you very much for working on this! This week's releases were right
on
> time.
> 
> I found one little issue in the announcement
> <https://postgis.net/2026/02/PostGIS-Patch-Releases/>: The NEWS file of
> 3.6.2 miss-linked to the one for 3.5.5
> 
> And, unfortunately, a bigger issue with a late patch on the 3.2 and 3.3
branch:
> <https://trac.osgeo.org/postgis/ticket/5998#comment:15> I will likely have
to
> skip packaging 3.2.9 and 3.3.9 in Postgres.App till this is settled.
> 
> Best regards
> Tobias


These two issues should be all set.

Thanks for reporting,
Regina


From lr at pcorp.us  Thu Feb 12 07:09:31 2026
From: lr at pcorp.us (Regina Obe)
Date: Thu, 12 Feb 2026 10:09:31 -0500
Subject: ERROR: Could not add geog_brin_inclusion_merge to
 brin_geography_inclusion_ops..null value in column "refobjid" (Re: Do you use
 PostGIS BRIN?)
In-Reply-To: <aY3fWcgRBUH38Wqa@pryzbyj2023>
References: <CAG29aDs6kiN1J6-s=3ZPA+NYdRVYJ0JpUmkPjjSdjCL+Bf6q5Q@mail.gmail.com>
 <006501db6089$c7e1c650$57a552f0$@pcorp.us>
 <8e400fa1-6c2d-4331-ab3d-64741aae8ff2@vondra.me>
 <5C4D43C4-62B7-4C73-817C-40FF8B6EF733@cleverelephant.ca>
 <e3839437-da80-4afa-81d8-3851bb82112d@vondra.me>
 <F9C53B87-E1B3-4391-B30E-90CD5D1FB46F@cleverelephant.ca>
 <Z8SuG0uwwEGjLRzK@pryzbyj2023> <002201db8bbd$70d81210$52883630$@pcorp.us>
 <Z8Tal9z539mBY_7B@pryzbyj2023> <003c01db8bc5$e79c9b20$b6d5d160$@pcorp.us>
 <aY3fWcgRBUH38Wqa@pryzbyj2023>
Message-ID: <001501dc9c31$97ce4300$c76ac900$@pcorp.us>

Justin,

Remind me do you always have this issue when upgrading older customers
(those who have been running PostGIS since at least PostgreSQL 9.3) or only
with some customers?

> -----Original Message-----
> From: Justin Pryzby <pryzby at telsasoft.com>
> Sent: Thursday, February 12, 2026 9:11 AM
> To: lr at pcorp.us
> Cc: Paul Ramsey <pramsey at cleverelephant.ca>; postgis-
> devel at lists.osgeo.org
> Subject: Re: ERROR: Could not add geog_brin_inclusion_merge to
> brin_geography_inclusion_ops..null value in column "refobjid" (Re: Do you
use
> PostGIS BRIN?)
> 
> We hit this again while/after upgrading one of our remaining
pg17+postgis3.4
> customers to pg18+postgis3.6.
> 
> # SELECT postgis_full_version();
> postgis_full_version | POSTGIS="3.6.1 f533623" [EXTENSION] PGSQL="170"
> (procs need upgrade for use with PostgreSQL "180") GEOS="3.11.2-CAPI-
> 1.17.2" PROJ="7.1.1 NETWORK_ENABLED=OFF
> URL_ENDPOINT=https://cdn.proj.org
> USER_WRITABLE_DIRECTORY=/var/lib/pgsql/.local/share/proj
> DATABASE_PATH=/usr/proj71/share/proj/proj.db" LIBXML="2.9.1"
> LIBJSON="0.11" (core procs from "3.4.2 3.4.2" need upgrade)
> 
> $ rpm -qa postgis\*
> postgis34_17-3.4.2-4PGDG.el7.x86_64
> postgis36_18-3.6.1-1PGDG.el7.x86_64
> 
> # SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';
>   oid  | opcmethod |            opcname             | opcnamespace |
opcowner |
> opcfamily | opcintype | opcdefault | opckeytype
>
-------+-----------+--------------------------------+--------------+--------
--+-----------
> +-----------+------------+------------
>  21756 |      3580 | brin_geometry_inclusion_ops_2d |         2200 |
10 |
> 21746 |     27847 | t          |      27830
>  21768 |      3580 | brin_geometry_inclusion_ops_3d |         2200 |
10 |
> 21764 |     27847 | f          |      27859
>  21778 |      3580 | brin_geometry_inclusion_ops_4d |         2200 |
10 |
> 21774 |     27847 | f          |      27859
> 
> > Also, the data dir was originally initdb'd under centos (7, and
> > probably earlier versions before that), and most recently migrated to
> > debian (with the requisite reindex).
> 
> This time, the server is still running centos7.  I've built my own RPMs
for
> pg18 and postgis, since pgdg doesn't provides RPMs for new versions on old
> OSes.
> 
> Let me know if I can add anything else.
> 
> 
> On Sun, Mar 02, 2025 at 05:53:23PM -0500, lr at pcorp.us wrote:
> > Justin,
> >
> > Thanks.  So it looks like brin was never installed in one version of
> > yours and in your second the geography brin was never installed.
> >
> > We've had issues over the years with some BRIN installs being missing
> > or partly missing because of not catching pg_upgrade changes in
> > PostgreSQL version.
> >
> > Anyrate I'll try to catch this situation and install BRIN if it is
> > found to be missing.
> >
> > Thanks,
> > Regina
> >
> > > -----Original Message-----
> > > From: Justin Pryzby <pryzby at telsasoft.com>
> > > Sent: Sunday, March 2, 2025 5:24 PM
> > > To: lr at pcorp.us
> > > Cc: Paul Ramsey <pramsey at cleverelephant.ca>;
> > > postgis-devel at lists.osgeo.org
> > > Subject: Re: ERROR: Could not add geog_brin_inclusion_merge to
> > > brin_geography_inclusion_ops..null value in column "refobjid" (Re:
> > > Do you
> > use
> > > PostGIS BRIN?)
> > >
> > > On Sun, Mar 02, 2025 at 04:52:48PM -0500, lr at pcorp.us wrote:
> > > > I've ticketed this issue here:
> > > > https://trac.osgeo.org/postgis/ticket/5856
> > > >
> > > > I'm going to try to revise the upgrade script to account for this
> > scenario.
> > > >
> > > > Can you do me a favor, send me the output of this from your
> > > > problem
> > > > database:
> > > >
> > > > SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';
> > >
> > > The DB where we hit the error says:
> > >
> > > ts=# SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE
> 'brin%';
> > >   oid  | opcmethod |            opcname             | opcnamespace |
> > opcowner |
> > > opcfamily | opcintype | opcdefault | opckeytype
> > >
> > -------+-----------+--------------------------------+--------------+--
> > -------+-----------+--------------------------------+--------------+--
> > -------+-----------+--------------------------------+--------------+--
> > -------+-----------+--------------------------------+--------------+--
> > --+-----------
> > > +-----------+------------+------------
> > >  17704 |      3580 | brin_geometry_inclusion_ops_2d |         2200 |
> > 10 |
> > > 17694 |     16419 | t          |      16454
> > >  17716 |      3580 | brin_geometry_inclusion_ops_3d |         2200 |
> > 10 |
> > > 17712 |     16419 | f          |      16458
> > >  17726 |      3580 | brin_geometry_inclusion_ops_4d |         2200 |
> > 10 |
> > > 17722 |     16419 | f          |      16458
> > > (3 rows)
> > >
> > > And the 2nd instance I mentioned which has no
> > > opcname='brin_geography_inclusion_ops' says:
> > >
> > > ts=# SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE
> > > 'brin%';  oid
> > > | opcmethod | opcname | opcnamespace | opcowner | opcfamily |
> > > | opcintype opcdefault | opckeytype
> > >
> > -----+-----------+---------+--------------+----------+-----------+----
> > -----+-----------+---------+--------------+----------+-----------+----
> > -----+-----------+---------+--------------+----------+-----------+--
> > > (0 rows)
> 
> --
> Justin Pryzby
> System Administrator
> Telsasoft
> +1-952-707-8581


From pryzby at telsasoft.com  Thu Feb 12 08:05:12 2026
From: pryzby at telsasoft.com (Justin Pryzby)
Date: Thu, 12 Feb 2026 10:05:12 -0600
Subject: ERROR:  Could not add geog_brin_inclusion_merge to
 brin_geography_inclusion_ops..null value in column "refobjid" (Re: Do you
 use PostGIS BRIN?)
In-Reply-To: <001501dc9c31$97ce4300$c76ac900$@pcorp.us>
References: <8e400fa1-6c2d-4331-ab3d-64741aae8ff2@vondra.me>
 <5C4D43C4-62B7-4C73-817C-40FF8B6EF733@cleverelephant.ca>
 <e3839437-da80-4afa-81d8-3851bb82112d@vondra.me>
 <F9C53B87-E1B3-4391-B30E-90CD5D1FB46F@cleverelephant.ca>
 <Z8SuG0uwwEGjLRzK@pryzbyj2023>
 <002201db8bbd$70d81210$52883630$@pcorp.us>
 <Z8Tal9z539mBY_7B@pryzbyj2023>
 <003c01db8bc5$e79c9b20$b6d5d160$@pcorp.us>
 <aY3fWcgRBUH38Wqa@pryzbyj2023>
 <001501dc9c31$97ce4300$c76ac900$@pcorp.us>
Message-ID: <aY36OGc2GrTALjuk@pryzbyj2023>

I've hit this 2 or 3 times now on different customers.  We usually
pg_upgrade to new major versions pretty quickly after they're released,
and maybe this issue is fallout from that.

This instance started with pg14 and was pg_upgraded every year since
then.  This is the version history for postgres:

postgres=# SELECT t::date, name, setting FROM pg_settings_snap WHERE name='server_version_num' ORDER BY 1;
     t      |        name        | setting 
------------+--------------------+---------
 2021-11-12 | server_version_num | 140000
 2022-02-11 | server_version_num | 140001
 2022-05-13 | server_version_num | 140002
 2022-06-20 | server_version_num | 140003
 2022-08-12 | server_version_num | 140004
 2022-10-20 | server_version_num | 140005
 2022-11-11 | server_version_num | 150000
 2023-02-21 | server_version_num | 150001
 2023-05-11 | server_version_num | 150002
 2023-08-10 | server_version_num | 150003
 2023-09-20 | server_version_num | 150004
 2023-11-07 | server_version_num | 160000
 2024-02-06 | server_version_num | 160001
 2024-05-10 | server_version_num | 160002
 2024-08-09 | server_version_num | 160003
 2024-09-30 | server_version_num | 160004
 2024-11-12 | server_version_num | 170000
 2024-11-20 | server_version_num | 170001
 2025-02-19 | server_version_num | 170002
 2025-05-06 | server_version_num | 170004
 2025-08-20 | server_version_num | 170005
 2026-02-12 | server_version_num | 170006
 2026-02-12 | server_version_num | 180002

Here's the available version history for postgis:

$ sudo grep gis /var/log/yum.log-* /var/log/yum.log
/var/log/yum.log-20230101:Oct 20 18:08:51 Installed: postgis33_15-3.3.1-2.rhel7.x86_64
/var/log/yum.log-20230101:Oct 20 18:08:51 Installed: postgis33_15-client-3.3.1-2.rhel7.x86_64
/var/log/yum.log-20240101:Sep 20 05:43:25 Installed: postgis34_16-3.4.0-1PGDG.el7.x86_64
/var/log/yum.log-20240101:Nov 30 03:45:49 Updated: postgis34_16-3.4.1-1PGDG.el7.x86_64
/var/log/yum.log-20250101:Aug 09 05:42:49 Updated: postgis34_16-3.4.2-1PGDG.el7.x86_64
/var/log/yum.log-20250101:Sep 30 04:57:32 Installed: postgis34_17-3.4.2-4PGDG.el7.x86_64
/var/log/yum.log:Feb 10 05:20:59 Installed: postgis36_18-3.6.1-1PGDG.el7.x86_64

This package is still installed, and might indicate the oldest postgis
that it started with:
postgis31_14-docs-3.1.4-1.rhel7.x86_64


On Thu, Feb 12, 2026 at 10:09:31AM -0500, Regina Obe wrote:
> Justin,
> 
> Remind me do you always have this issue when upgrading older customers
> (those who have been running PostGIS since at least PostgreSQL 9.3) or only
> with some customers?
> 
> > -----Original Message-----
> > From: Justin Pryzby <pryzby at telsasoft.com>
> > Sent: Thursday, February 12, 2026 9:11 AM
> > To: lr at pcorp.us
> > Cc: Paul Ramsey <pramsey at cleverelephant.ca>; postgis-
> > devel at lists.osgeo.org
> > Subject: Re: ERROR: Could not add geog_brin_inclusion_merge to
> > brin_geography_inclusion_ops..null value in column "refobjid" (Re: Do you
> use
> > PostGIS BRIN?)
> > 
> > We hit this again while/after upgrading one of our remaining
> pg17+postgis3.4
> > customers to pg18+postgis3.6.
> > 
> > # SELECT postgis_full_version();
> > postgis_full_version | POSTGIS="3.6.1 f533623" [EXTENSION] PGSQL="170"
> > (procs need upgrade for use with PostgreSQL "180") GEOS="3.11.2-CAPI-
> > 1.17.2" PROJ="7.1.1 NETWORK_ENABLED=OFF
> > URL_ENDPOINT=https://cdn.proj.org
> > USER_WRITABLE_DIRECTORY=/var/lib/pgsql/.local/share/proj
> > DATABASE_PATH=/usr/proj71/share/proj/proj.db" LIBXML="2.9.1"
> > LIBJSON="0.11" (core procs from "3.4.2 3.4.2" need upgrade)
> > 
> > $ rpm -qa postgis\*
> > postgis34_17-3.4.2-4PGDG.el7.x86_64
> > postgis36_18-3.6.1-1PGDG.el7.x86_64
> > 
> > # SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';
> >   oid  | opcmethod |            opcname             | opcnamespace |
> opcowner |
> > opcfamily | opcintype | opcdefault | opckeytype
> >
> -------+-----------+--------------------------------+--------------+--------
> --+-----------
> > +-----------+------------+------------
> >  21756 |      3580 | brin_geometry_inclusion_ops_2d |         2200 |
> 10 |
> > 21746 |     27847 | t          |      27830
> >  21768 |      3580 | brin_geometry_inclusion_ops_3d |         2200 |
> 10 |
> > 21764 |     27847 | f          |      27859
> >  21778 |      3580 | brin_geometry_inclusion_ops_4d |         2200 |
> 10 |
> > 21774 |     27847 | f          |      27859
> > 
> > > Also, the data dir was originally initdb'd under centos (7, and
> > > probably earlier versions before that), and most recently migrated to
> > > debian (with the requisite reindex).
> > 
> > This time, the server is still running centos7.  I've built my own RPMs
> for
> > pg18 and postgis, since pgdg doesn't provides RPMs for new versions on old
> > OSes.
> > 
> > Let me know if I can add anything else.
> > 
> > 
> > On Sun, Mar 02, 2025 at 05:53:23PM -0500, lr at pcorp.us wrote:
> > > Justin,
> > >
> > > Thanks.  So it looks like brin was never installed in one version of
> > > yours and in your second the geography brin was never installed.
> > >
> > > We've had issues over the years with some BRIN installs being missing
> > > or partly missing because of not catching pg_upgrade changes in
> > > PostgreSQL version.
> > >
> > > Anyrate I'll try to catch this situation and install BRIN if it is
> > > found to be missing.
> > >
> > > Thanks,
> > > Regina
> > >
> > > > -----Original Message-----
> > > > From: Justin Pryzby <pryzby at telsasoft.com>
> > > > Sent: Sunday, March 2, 2025 5:24 PM
> > > > To: lr at pcorp.us
> > > > Cc: Paul Ramsey <pramsey at cleverelephant.ca>;
> > > > postgis-devel at lists.osgeo.org
> > > > Subject: Re: ERROR: Could not add geog_brin_inclusion_merge to
> > > > brin_geography_inclusion_ops..null value in column "refobjid" (Re:
> > > > Do you
> > > use
> > > > PostGIS BRIN?)
> > > >
> > > > On Sun, Mar 02, 2025 at 04:52:48PM -0500, lr at pcorp.us wrote:
> > > > > I've ticketed this issue here:
> > > > > https://trac.osgeo.org/postgis/ticket/5856
> > > > >
> > > > > I'm going to try to revise the upgrade script to account for this
> > > scenario.
> > > > >
> > > > > Can you do me a favor, send me the output of this from your
> > > > > problem
> > > > > database:
> > > > >
> > > > > SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE 'brin%';
> > > >
> > > > The DB where we hit the error says:
> > > >
> > > > ts=# SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE
> > 'brin%';
> > > >   oid  | opcmethod |            opcname             | opcnamespace |
> > > opcowner |
> > > > opcfamily | opcintype | opcdefault | opckeytype
> > > >
> > > -------+-----------+--------------------------------+--------------+--
> > > -------+-----------+--------------------------------+--------------+--
> > > -------+-----------+--------------------------------+--------------+--
> > > -------+-----------+--------------------------------+--------------+--
> > > --+-----------
> > > > +-----------+------------+------------
> > > >  17704 |      3580 | brin_geometry_inclusion_ops_2d |         2200 |
> > > 10 |
> > > > 17694 |     16419 | t          |      16454
> > > >  17716 |      3580 | brin_geometry_inclusion_ops_3d |         2200 |
> > > 10 |
> > > > 17712 |     16419 | f          |      16458
> > > >  17726 |      3580 | brin_geometry_inclusion_ops_4d |         2200 |
> > > 10 |
> > > > 17722 |     16419 | f          |      16458
> > > > (3 rows)
> > > >
> > > > And the 2nd instance I mentioned which has no
> > > > opcname='brin_geography_inclusion_ops' says:
> > > >
> > > > ts=# SELECT * FROM pg_catalog.pg_opclass WHERE opcname ILIKE
> > > > 'brin%';  oid
> > > > | opcmethod | opcname | opcnamespace | opcowner | opcfamily |
> > > > | opcintype opcdefault | opckeytype
> > > >
> > > -----+-----------+---------+--------------+----------+-----------+----
> > > -----+-----------+---------+--------------+----------+-----------+----
> > > -----+-----------+---------+--------------+----------+-----------+--
> > > > (0 rows)

-- 
Justin Pryzby
System Administrator
Telsasoft
+1-952-707-8581