We currently don't recognise the PostGIS GEOMETRY type, which is a user-defined type stored in an arbitrary schema (e.g. public.geometry or postgis.geometry). The information_schema reports it as such, and we can't map it to anything. A workaround is to configure:

<forcedType>
    <name>GEOMETRY</name>
    <includeTypes>geometry</includeTypes>
</forcedType>

Not too impressive. But given there's a slight chance of the PostGIS GEOMETRY type colliding with an ordinary user-defined type, so we must choose our heuristics carefully.

This should be fixed soon, in a 3.16 patch release.