#5231 closed defect (fixed)
PG15 no longer compiles against PostGIS 3.2 - 3.3 because SQL/JSON removed upstream
Reported by: | robe | Owned by: | robe |
---|---|---|---|
Priority: | blocker | Milestone: | PostGIS 3.2.4 |
Component: | postgis | Version: | master |
Keywords: | Cc: |
Description
They seemed to have made further changes to PG15 beta that broke geojson again.
I thought it was my PG cleanup, but this error has been happening before that and after debbie and GHA ci had refreshed their PG15s
Looks like it's probably this commit - https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=96ef3237bf741c12390003e90a4d7115c0c854b7
Revert SQL/JSON features The reverts the following and makes some associated cleanups:
and I was so looking forward to those changes.
Change History (9)
comment:1 by , 2 years ago
Milestone: | PostGIS 3.3.1 → PostGIS 3.2.4 |
---|---|
Summary: | PG15 no longer compiles against PostGIS 3.3 and PostGIS 3.4 → PG15 no longer compiles against PostGIS 3.2 - 3.4 |
comment:2 by , 2 years ago
Summary: | PG15 no longer compiles against PostGIS 3.2 - 3.4 → PG15 no longer compiles against PostGIS 3.2 - 3.4 because SQL/JSON removed upstream |
---|
comment:7 by , 2 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:8 by , 2 years ago
related discussion of this is here - https://www.postgresql.org/message-id/flat/abd9b83b-aa66-f230-3d6d-734817f0995d%40postgresql.org
comment:9 by , 2 years ago
Summary: | PG15 no longer compiles against PostGIS 3.2 - 3.4 because SQL/JSON removed upstream → PG15 no longer compiles against PostGIS 3.2 - 3.3 because SQL/JSON removed upstream |
---|
Note:
See TracTickets
for help on using tickets.
just occurred to me I had backported to PostGIS 3.2 too so that has to be fixed.
As a quick fix, I'll change all those ifdefs to PG 17, and put back if PG 16 keeps the functionality, but they had ripped out of PG16 too. So this will be a partial revert of #5123