[PostGIS] #6063: postgis_restore ignoring dchemaname when migrating database

[PostGIS]

#6063: postgis_restore ignoring dchemaname when migrating database
-----------------------------+---------------------------
 Reporter:  robopost         |      Owner:  strk
     Type:  defect           |     Status:  new
 Priority:  medium           |  Milestone:  PostGIS 3.5.6
Component:  upgrade/hard     |    Version:  3.5.x
 Keywords:  postgis_restore  |
-----------------------------+---------------------------
 Hello,

 during a Migration from postgis 3.1 to 3.5 using the Script
 postgis_restore i found a strange behaviour:

 In our Database we had a Table named layer in a Schema that didn't
 belong to postgis. After the run of postgis_restore the Table didn't exist
 and the Import had errors when it tried load Data in this Table. In a
 verbose run i saw this:

 SKIP: TABLE layer

 Here postgis_restore seemed to ignore the Schema.

 Is it common practice not to use Tables named layer in a postgis enabled
 database or could this be a Bug?

 Yours sincerely

 Robert Aussem
-- 
Ticket URL: <https://trac.osgeo.org/postgis/ticket/6063>
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.