[postgis-users] Workaround for postgis raster / pg_dump problem. (bug #2485)

Graeme B. Bell grb at skogoglandskap.no
Thu Jul 31 06:54:35 PDT 2014

Hi all

With postgres 9.4 and a mandatory pg_dump/pg_restore coming soon, I wrote a quick workaround for the pg_dump bug that is affecting postgis raster. Hope this little bit of code is useful for others too.

The bug in question is: http://trac.osgeo.org/postgis/ticket/2485

The basic idea is that since pg_dump is generating a search path that can't find the raster functions (because they're in public), we can move every raster to a temporary name, stuff the rasters into the public schema, pg_dump, pg_restore, then put everything back where it belongs afterwards.

I've put it here:  https://gist.github.com/gbb/d551c92edf2cd8371c09

If you find any errors, please let me know asap.


More information about the postgis-users mailing list