#3918 closed enhancement (wontfix)
postgis_extension_unpackage()
| Reported by: | strk | Owned by: | strk |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS 3.0.0 |
| Component: | build | Version: | master |
| Keywords: | Cc: |
Description
This ticket is to provide a function to "unpackage" the postgis extension(s). This may be seen as a complement to "CREATE EXTENSION .. FROM unpackaged". See also #3896
Change History (7)
comment:1 by , 7 years ago
| Milestone: | → PostGIS 2.5.0 |
|---|---|
| Type: | defect → enhancement |
| Version: | 2.4.x → trunk |
comment:2 by , 7 years ago
comment:3 by , 7 years ago
The actual error I was experiencing was actually a double-registration of objects in the extension upon "CREATE FROM UNPACKAGED", as reported on https://trac.osgeo.org/postgis/ticket/3913#comment:4
A postgis_extension_unpackage() would help testing unpackage/repackage path...
comment:4 by , 7 years ago
| Component: | postgis → build/upgrade/install |
|---|---|
| Owner: | changed from to |
comment:5 by , 6 years ago
| Milestone: | PostGIS 2.5.0 → PostGIS 3.0.0 |
|---|
comment:6 by , 5 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
comment:7 by , 2 years ago
We don't wont this EVER as a user facing function. It's something PostgreSQL upstream has expressed they don't want people running unpackaged extensions.
If you feel you need this for testing, then have as a testing function and drop it after use.
Note:
See TracTickets
for help on using tickets.
Such a function would also help testing upgrades from unpackaged, as that part is understested. For example it looks to me that the
extensions/opt_out.shis failing to unpackage theraster_columnsview