[postgis-tickets] [PostGIS] #4291: [raster] Calling ST_Intersects in matviews causes unrestorable pg_dump

[PostGIS]

#4291: [raster] Calling ST_Intersects in matviews causes unrestorable pg_dump
---------------------+---------------------------
 Reporter:  nblumoe  |      Owner:  Bborie Park
     Type:  defect   |     Status:  new
 Priority:  medium   |  Milestone:  PostGIS 2.5.2
Component:  raster   |    Version:  2.4.x
 Keywords:           |
---------------------+---------------------------
 I am using materialized views which include calls to ST_Intersects. After
 dumping them via pg_dump, I am not able to restore them with pg_restore
 because refreshing the mat views fails:

 {{{
 pg_restore: [archiver (db)] Error while PROCESSING TOC:
 pg_restore: [archiver (db)] Error from TOC entry 7965; 0 74457
 MATERIALIZED VIEW DATA company_level_production_risk_all_sectors postgres
 pg_restore: [archiver (db)] could not execute query: ERROR:  type
 "geometry" does not exist
 LINE 1:  SELECT $1::geometry OPERATOR(public.&&) $2 AND public._st_i...
                     ^
 QUERY:   SELECT $1::geometry OPERATOR(public.&&) $2 AND
 public._st_intersects($2, $1, $3)
 CONTEXT:  SQL function "st_intersects" during inlining
     Command was: REFRESH MATERIALIZED VIEW
 public.company_level_production_risk_all_sectors;
 }}}

 This looks similar to https://trac.osgeo.org/postgis/ticket/3012 and might
 be caused by a search_path problem as geometry is referred to without the
 schema name.

 The invocation is on ST_Intersects(raster, geometry)

-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/4291>
PostGIS <http://trac.osgeo.org/postgis/>
The PostGIS Trac is used for bug, enhancement & task tracking, a user and developer wiki, and a view into the subversion code repository of PostGIS project.