Possible Bug in postgis_restore

[Aussem, Robert (LGL extern)]

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20260326/2e173be7/attachment.htm>