#4975 closed defect (fixed)
PostGIS upgrade should not use temp tables as that is banned by some security policies
Reported by: | robe | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS 3.2.0 |
Component: | build | Version: | 2.5.x -- EOL |
Keywords: | Cc: |
Description
Aiven proposed a solution using a temp function _postgis_upgrade_info() instead of a temp table _postgis_upgrade_info. I haven't tested the patch yet. Will affect all our upgrades so needs careful testing.
Change History (4)
comment:1 by , 3 years ago
comment:3 by , 3 years ago
Fine by me, but please update the CI badges on the wiki or we can't trust them
comment:4 by , 3 years ago
I wonder if we could use the same approach for the dumper: #4975
Version 0, edited 3 years ago by (next)
Note:
See TracTickets
for help on using tickets.
Related issues this should solve:
RDS Mailing List issue: https://www.mail-archive.com/postgis-users@lists.osgeo.org/msg08353.html
Heroku also seems to have run into this error: https://stackoverflow.com/questions/54213361/update-postgis-extensions-on-heroku + https://trac.osgeo.org/postgis/ticket/4186 mention this error message
PostGIS Users list: https://lists.osgeo.org/pipermail/postgis-users/2020-May/044225.html