Opened 8 years ago

Closed 2 years ago

Last modified 2 years ago

#1816 closed enhancement (fixed)

SVN updates applied in PostgreSQL 9.1+

Reported by: darkblueb Owned by: robe
Priority: medium Milestone: PostGIS 2.5.0
Component: build/upgrade/install Version: 2.0.x
Keywords: Cc:


currently, to build and test new code from topology svn, either tricky sym links or a complete dump and reload of the test database appear to be necessary when using CREATE EXTENSION sort of libraries, such as postgis_topology.

wouldn't it be better to have a way to cleanly reload topology after building and installing? same for other EXTENSION based additions, most likely...

Change History (4)

comment:1 Changed 8 years ago by robe

Component: postgisbuild/upgrade/install
Owner: changed from pramsey to strk
Summary: SVN updates applied in PostgreSQL 9+SVN updates applied in PostgreSQL 9.1+

Yah that's one of the downsides of extension that it won't upgrade from same version to same version. It's only an issue for svn version of course.

As a hack -- what I do is change the control file to be something like PostGIS 2.0.1SVNrxyz

and then create a copy of the script to be from my old to faked version path.

I agree we should come up with something more elegant or get in the habit of having interim version stops whenever we change the scripts. strk won't like that :).

One thought i had is to have an unbundle script. Basically a script that unbundles your postgis from extension so you can run the regular upgrade script and then rebundles it.

That we could achieve in one step I guess. It's essentially how we get the update from extension to work. But it won't have the nice "ALTER EXTENTION postgis UPDATE To" feel. Live on the edge have to pay some tolls :)

comment:2 Changed 8 years ago by robe

Owner: changed from strk to robe

comment:3 Changed 3 years ago by robe

Milestone: PostGIS FuturePostGIS Fund Me

Milestone renamed

comment:4 Changed 2 years ago by robe

Milestone: PostGIS Fund MePostGIS 2.5.0
Resolution: fixed
Status: newclosed

was fixed with the yoyo 2.5.0next, 2.5.0

and the

SELECT postgis_extensions_upgrade();

new in PostGIS 2.5.0 does the yo yo dance too so you don't have to.

Last edited 2 years ago by robe (previous) (diff)
Note: See TracTickets for help on using tickets.